[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EDEF05F.4020901@linux.vnet.ibm.com>
Date: Wed, 07 Dec 2011 12:49:35 +0800
From: Michael Wang <wangyun@...ux.vnet.ibm.com>
To: Joe Perches <joe@...ches.com>
CC: jeffrey.t.kirsher@...el.com,
"e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"wangyunlinux@...il.com" <wangyunlinux@...il.com>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
Subject: Re: [PATCH v2] e1000e: Assign true and false to bool type variable
instead of 1 and 0
On 12/07/2011 12:14 PM, Joe Perches wrote:
> On Tue, 2011-12-06 at 19:43 -0800, Jeff Kirsher wrote:
>> On Tue, 2011-12-06 at 18:33 -0800, Michael Wang wrote:
>>> From: Michael Wang <wangyun@...ux.vnet.ibm.com>
>>> Use true and false instead of 1 and 0 when assign value to a bool type
>>> variable.
>> Thanks Michael, I have added your patch to my queue of e1000e patches.
>
> There are more of these uses in intel drivers.
>
> Perhaps you could run this cocci/spatch
> on drivers/net/ethernet/intel/...
>
> $ cat bool.cocci
> @@
> bool b;
> @@
>
> -b = 0;
> +b = false;
>
> @@
> bool b;
> @@
>
> -b = 1;
> +b = true;
>
> $ git ls-files drivers/net/ethernet/intel/ | grep "\.c$" | while read file ; do spatch -in_place -sp_file bool.cocci $file ; done
>
>
Hi, Joe
I think there are lots of such cases in kernel, and I think it is a
legacy issue with some story in it.
The reason I only change the e1000e is that the patch I send before will
broken the style of e1000e, because it's using true and false, not 1 and 0.
I think this will be a huge work if we want to correct all these cases,
and I think the good way is to separate the work to small pieces and
finish them slowly.
Thanks,
Michael Wang
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists