From: Andrew Lunn <andrew.lunn@ascom.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] [batman-adv] bitarray.[ch] Linux coding style cleanup
Date: Tue, 14 Jul 2009 15:20:04 +0200 [thread overview]
Message-ID: <20090714132004.GN19071@ma.tech.ascom.ch> (raw)
In-Reply-To: <20090714130926.GM19071@ma.tech.ascom.ch>
On Tue, Jul 14, 2009 at 03:09:26PM +0200, Andrew Lunn wrote:
> Fix all the warnings generated by the 2.6.29 checkpatch script about
> violations of the Linux coding style in the bitarray.[ch]
> files.
This patch is to probe the waters a little. Marek has said off the
list that it has been decided that the batman-adv code should conform
to the Linux kernel coding standard. Much of the code is currently
not! What i dislike most in the current code base is the long
lines. The coding style says that lines should be less than 80
characters long.
This patch cleans up two files, making them pass the coding style
checks for 2.6.29, the latest kernel code i have hanging around on my
machine.
What are peoples opinion about this? Should i spend a little time
cleaning up all the files? Some code needs refactoring a little, to
reducing the nesting, creating more helper functions, but mostly its
white space changes. However such changes can cause pain when trying
to merge in other work people who diff's are against before the
cleanup. Does anybody have any major patches?
Thanks
Andrew
next prev parent reply other threads:[~2009-07-14 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 13:09 [B.A.T.M.A.N.] [batman-adv] bitarray.[ch] Linux coding style cleanup Andrew Lunn
2009-07-14 13:20 ` Andrew Lunn [this message]
2009-07-14 13:32 ` Antoine van Gelder
2009-07-14 13:57 ` [B.A.T.M.A.N.] [batman-adv] bitarray.[ch] Linux coding style cleanupy Andrew Lunn
2009-07-14 13:38 ` [B.A.T.M.A.N.] [batman-adv] bitarray.[ch] Linux coding style cleanup Sven Eckelmann
2009-07-14 14:48 ` Marek Lindner
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=20090714132004.GN19071@ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox