[lkml]   [2012]   [Feb]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Cleaning up code formatting errors in net/wireless pointed out by checkpatch.
On 17 February 2012 13:47, David Laight <> wrote:
>> These are mostly minor changes and they are being sent as one
>> patch only in order to cause the smallest amount of disruption.
> A lot of these changes don't seem to match what I thought the
> linux kernel code style is.
> eg:
>>  void cfg80211_bss_age(struct cfg80211_registered_device *dev,
>> -                      unsigned long age_secs);
>> +                   unsigned long age_secs);
> Args no longer lined up.

It's ligned up here, perhaps mine (or yours) mail client is screwing
something up. This one was basically using tabs where they were
supposed to be.

>> -             pos = (u8 *) & hdr->addr4;
>> +             pos = (u8 *) &hdr->addr4;
> no space after cast?

There is a space there. The problem pointed by checkpatch was the
space between '&' and hdr.

>> -     p1 = (u8*)(ht_capa);
>> +     p1 = (u8 *)(ht_capa);
> Still extra ().
> I'm also not sure (personally) this sort of churn is useful.

As mentioned, those are mostly minor changes based on checkpatch's
output. Cleaning up only things that were specifically marked as
errors (so the extra parentheses there were not reported).

I don't think having lots of this kind of churn useful, thats why I
sent one patch only for the entire directory trying to clean up as
much as possible. There are some errors that I didn't clean up, but
they are mostly where an option was made on the source code to keep
code in a more readable way.


>        David

Luís Felipe Strano Moraes
Project Manager @ ProFUSION embedded systems
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2012-02-17 16:59    [W:0.138 / U:2.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site