All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Joe Perches <joe@perches.com>
Cc: netdev@vger.kernel.org, jeff@garzik.org, davem@davemloft.net,
	arjan@linux.intel.com, shemminger@linux-foundation.org
Subject: Re: [PATCH 1/2] [RFC] NET: Implement a standard ndev_printk family
Date: Mon, 11 Jun 2007 15:01:59 -0700	[thread overview]
Message-ID: <466DC657.2030401@intel.com> (raw)
In-Reply-To: <1181598880.6020.8.camel@localhost>

Joe Perches wrote:
> On Mon, 2007-06-11 at 14:37 -0700, Auke Kok wrote:
>> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
>> index 3a70f55..d185f41 100644
>> --- a/include/linux/netdevice.h
>> +++ b/include/linux/netdevice.h
>> @@ -540,6 +540,8 @@ struct net_device
>>  	struct device		dev;
>>  	/* space for optional statistics and wireless sysfs groups */
>>  	struct attribute_group  *sysfs_groups[3];
>> +
>> +	int			msg_enable;
>>  };
>>  #define to_net_dev(d) container_of(d, struct net_device, dev)
>>  
> 
> msg_enable is more frequently defined in drivers/net as u32 not int.
> 
> egrep -r -w --include=*.[ch] "u32[[:space:]]+msg_enable" drivers/net | wc -l
> egrep -r -w --include=*.[ch] "int[[:space:]]+msg_enable" drivers/net | wc -l
> 
> 29 to 5

yes, we're only using the bottom 15 bits anyway, but the net_device struct 
consistently uses 'int' style members, leaving it up to the compiler to pick an 
appropriate size for each arch. That was the reason I chose int here.

Auke

  reply	other threads:[~2007-06-11 22:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 21:37 [PATCH 1/2] [RFC] NET: Implement a standard ndev_printk family Auke Kok
2007-06-11 21:37 ` [PATCH 2/2] [RFC] NET: Convert several drivers to ndev_printk Auke Kok
2007-06-11 21:52 ` [PATCH 1/2] [RFC] NET: Implement a standard ndev_printk family Kok, Auke
2007-06-11 21:54 ` Joe Perches
2007-06-11 22:01   ` Kok, Auke [this message]
2007-06-11 22:24     ` Joe Perches
2007-06-11 22:00 ` Randy Dunlap
2007-06-11 22:04   ` Kok, Auke
2007-06-11 22:19 ` Stephen Hemminger
2007-06-11 22:43   ` Kok, Auke
  -- strict thread matches above, loose matches on Subject: below --
2007-06-08 22:00 Auke Kok
2007-06-08 23:24 ` Stephen Hemminger
2007-06-08 23:42   ` Kok, Auke
2007-06-09  0:10     ` Stephen Hemminger
2007-06-09  3:06       ` Kok, Auke
2007-06-09  3:18       ` Kok, Auke
2007-06-11 17:30       ` Kok, Auke
2007-06-11 17:50         ` Stephen Hemminger
2007-06-11 18:28           ` Joe Perches
2007-06-11 20:28             ` Kok, Auke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=466DC657.2030401@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=joe@perches.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.