From: Eric Dumazet <eric.dumazet@gmail.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
Cc: Joe Perches <joe@perches.com>,
Linux Kernel Developers <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: warning: massive change to conditional coding style in net?
Date: Tue, 01 Dec 2009 17:49:36 +0100 [thread overview]
Message-ID: <4B154920.40203@gmail.com> (raw)
In-Reply-To: <4B153F9B.7050502@gmail.com>
William Allen Simpson a écrit :
> Joe Perches wrote:
>> If it makes getting tcp cookies accepted difficult,
>> a reversion is simple. That style isn't as important.
>>
> Then why make an *un*important (yet sweeping) change?
Because this is time :
We usually makes cleanup patches just before the release
of a new linux kernel, to minimize effects on developer trees.
We know linux-2.6.32 is about to be released by Linus,
and all major 2.6.33 patches are already queued in net-next-2.6
to be pushed to Linus as soon as the window opens.
This is the perfect time for cleanups. Doing cleanups is a good
way to learn linux code, before doing more complex things.
If you take a look at queued patches in net-next-2.6, maybe less
than 5 % are cleanups.
But this rule can be changed, if your patches are ready for inclusion,
David might revert the jumbo cleanup to ease your job. Just ask.
next prev parent reply other threads:[~2009-12-01 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 10:36 warning: massive change to conditional coding style in net? William Allen Simpson
2009-11-30 13:44 ` Jarek Poplawski
2009-11-30 13:54 ` Alan Cox
2009-11-30 19:39 ` Jarek Poplawski
2009-11-30 17:56 ` Joe Perches
2009-12-01 16:08 ` William Allen Simpson
2009-12-01 16:49 ` Eric Dumazet [this message]
2009-12-01 17:43 ` Jarek Poplawski
2009-11-30 20:36 ` David Miller
2009-12-01 17:56 ` William Allen Simpson
2009-12-01 18:30 ` Eric Dumazet
2009-12-01 23:28 ` David Miller
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=4B154920.40203@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=william.allen.simpson@gmail.com \
/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).