Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932343Ab0GVOHb (ORCPT ); Thu, 22 Jul 2010 10:07:31 -0400 Received: from exchange.solarflare.com ([216.237.3.220]:10989 "EHLO exchange.solarflare.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759492Ab0GVOH1 (ORCPT ); Thu, 22 Jul 2010 10:07:27 -0400 Subject: Re: [PATCH net-next] sysfs: add attribute to indicate hw address assignment type From: Ben Hutchings To: Stefan Assmann Cc: David Miller , abadea@ixiacom.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, gospo@redhat.com, gregory.v.rose@intel.com, alexander.h.duyck@intel.com, leedom@chelsio.com, harald@redhat.com In-Reply-To: <4C483E8D.4080300@redhat.com> References: <4C458CB7.3030508@redhat.com> <4C458F50.4070200@ixiacom.com> <4C4593DA.9040207@redhat.com> <20100720.131839.134093789.davem@davemloft.net> <4C46AB60.5060008@redhat.com> <1279720478.2089.3.camel@achroite.uk.solarflarecom.com> <4C483E8D.4080300@redhat.com> Content-Type: text/plain Organization: Solarflare Communications Date: Thu, 22 Jul 2010 15:07:23 +0100 Message-Id: <1279807643.2104.1.camel@achroite.uk.solarflarecom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 (2.26.1-2.fc11) Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 Jul 2010 14:09:02.0204 (UTC) FILETIME=[6FCAF3C0:01CB29A7] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-6.000.1038-17520.005 X-TM-AS-Result: No--29.681700-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1629 Lines: 46 On Thu, 2010-07-22 at 14:50 +0200, Stefan Assmann wrote: > On 21.07.2010 15:54, Ben Hutchings wrote: > > On Wed, 2010-07-21 at 10:10 +0200, Stefan Assmann wrote: > >> I put Alex' idea into code for further discussion, keeping the names > >> mentioned here until we agree on the scope of this attribute. When we > >> have settled I'll post a patch with proper patch description. > > [...] > > > > Just a little nitpick: I think it would be clearer to use a more > > specific term like 'address source' or 'address assignment type' rather > > than 'address type'. > > Here's a proposal for the final patch. Looks good, but... [...] > /** > + * dev_hw_addr_random - Create random MAC and set device flag > + * @dev: pointer to net_device structure > + * @addr: Pointer to a six-byte array containing the Ethernet address > + * > + * Generate random MAC to be used by a device and set addr_assign_type > + * so the state can be read by sysfs and be used by udev. > + */ > +static inline void dev_hw_addr_random(struct net_device *dev, u8 *hwaddr) > +{ > + dev->addr_assign_type |= NET_ADDR_RANDOM; > + random_ether_addr(hwaddr); > +} [...] ...why '|=' and not '='? Ben. -- Ben Hutchings, Senior Software Engineer, Solarflare Communications Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/