From: Frans Pop <elendil@planet.nl>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jon Maloy <jon.maloy@ericsson.com>,
Samuel Ortiz <samuel@sortiz.org>,
e1000-devel@lists.sourceforge.net,
Per Liden <per.liden@ericsson.com>,
linuxppc-dev@ozlabs.org,
Allan Stephens <allan.stephens@windriver.com>
Subject: [PATCH 00/09] net: remove trailing spaces in messages
Date: Wed, 24 Mar 2010 18:40:15 +0100 [thread overview]
Message-ID: <201003241840.18701.elendil@planet.nl> (raw)
This is the second patchset to remove trailing spaces in kernel messages.
Patches in this set cover networking code, excepting wireless which will be
submitted in a separate set.
Patches have been rebased against current net-next.
Benefits are:
- general cleanup and consistency
- minor reduction in kernel size and user's log file size
- reduced annoyance for people writing logcheck rules
I have run the patches through checkpatch and included some fixes, but in
most cases the files are so horrible in general that fixing the warnings
purely for these changes doesn't make sense.
Shortstat:
56 files changed, 236 insertions(+), 236 deletions(-)
Frans Pop (9):
net: remove trailing space in messages
net/tipc: remove trailing space in messages
net/irda: remove trailing space in messages
net/ps3_gelic: remove trailing space in messages
net/smc91xx: remove trailing space in messages
net/tokenring: remove trailing space in messages
net/tulip: remove trailing space in messages
net/intel: remove trailing space in messages
net/various: remove trailing space in messages
Cheers,
FJP
next reply other threads:[~2010-03-24 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 17:40 Frans Pop [this message]
2010-03-24 17:57 ` [PATCH 4/9] net/ps3_gelic: remove trailing space in messages Frans Pop
2010-03-24 21:11 ` [PATCH 00/09] net: remove trailing spaces " David Miller
2010-03-24 21:30 ` Frans Pop
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=201003241840.18701.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=allan.stephens@windriver.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=per.liden@ericsson.com \
--cc=samuel@sortiz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).