[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100708.235314.241453003.davem@davemloft.net>
Date: Thu, 08 Jul 2010 23:53:14 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: horms@...ge.net.au
Cc: karl@...amoto.org, linux-atm-general@...ts.sourceforge.net,
netdev@...r.kernel.org, chas@....nrl.navy.mil
Subject: Re: [PATCH v4 1/9] atm: propagate signal changes via notifier
From: Simon Horman <horms@...ge.net.au>
Date: Fri, 9 Jul 2010 15:50:13 +0900
> On Thu, Jul 08, 2010 at 11:38:01PM -0700, David Miller wrote:
>> From: Karl Hiramoto <karl@...amoto.org>
>> Date: Fri, 09 Jul 2010 08:36:03 +0200
>>
>> > Ok, fixing it, but there are 100's of occurences in net/ like i had it. :-)
>>
>> I would be happy to see a patch which fixes them up :-)
>
> Really? By my calculations it would be an awful lot of churn.
>
> $ find net/ -type f -name "*.[chS]" | xargs grep "\/\* *$" | wc -l
> 6833
> $ find net/ -type f -name "*.[chS]" | xargs grep -l "\/\* *$" | wc -l
> 929
I didn't mean "one patch" which fixes them up :)
Done graudually in chunks over a period of time, it's not likely
to be so much churn.
This is how every other coding style malfeasance gets handled.
--
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