From: William Allen Simpson <william.allen.simpson@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
davem@davemloft.net,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH] net-ipv4-tcp.c-fix-warning-from-older-compilers.patch
Date: Fri, 11 Dec 2009 10:49:38 -0500 [thread overview]
Message-ID: <4B226A12.5070102@gmail.com> (raw)
In-Reply-To: <4B211452.40600@gmail.com>
Eric Dumazet wrote:
> This is not necessary, David already _did_ the thing, and _told_ so.
>
There doesn't seem to be a patch sent to the list, at least it didn't
show up in my mail, nor is it in the archive. Such mistakes happen.
> You probably missed fact we are in merge window, so fixes (and only fixes)
> are pushed into net-2.6 tree.
>
That's my understanding. I'd asked a question earlier which tree to
patch against (which he didn't answer), but a later message was more
helpful and detailed.
> When Linus closes this merge window (issuing a linux-2.6.33-rc1 tag),
> then David re-opens net-next-2.6 tree for new stuff.
>
That's my understanding, thanks again. (This isn't new stuff.)
> http://git2.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commitdiff;h=3dc789320e1b310cb505dcd94512c279abcd5e1c
>
Well, I'll be darned! There must be some list that you're on that sends
out such notifications....
Not a good patch, as it accidentally removed the section comment. And it
fails to describe or test against buffer overruns.
So, he'll have no problems backing out his patch and adding mine.
next prev parent reply other threads:[~2009-12-11 15:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200912090045.nB90jTaO010647@imap1.linux-foundation.org>
2009-12-09 1:45 ` + net-ipv4-tcpc-fix-warning.patch added to -mm tree William Allen Simpson
2009-12-09 2:08 ` Andrew Morton
2009-12-09 4:07 ` David Miller
2009-12-10 13:48 ` William Allen Simpson
2009-12-10 14:16 ` [PATCH] net-ipv4-tcp.c-fix-warning-from-older-compilers.patch William Allen Simpson
2009-12-10 14:31 ` Ben Hutchings
2009-12-11 15:30 ` William Allen Simpson
2009-12-11 15:38 ` [PATCH v2] net-ipv4-tcp.c-fix-warning-for-older-compilers.patch William Allen Simpson
2009-12-10 15:31 ` [PATCH] net-ipv4-tcp.c-fix-warning-from-older-compilers.patch Eric Dumazet
2009-12-10 21:46 ` David Miller
2009-12-11 6:50 ` Jarek Poplawski
2009-12-11 15:51 ` William Allen Simpson
2009-12-11 19:25 ` Jarek Poplawski
2009-12-11 22:25 ` David Miller
2009-12-11 15:49 ` William Allen Simpson [this message]
2009-12-11 22:24 ` David Miller
2009-12-10 21:43 ` 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=4B226A12.5070102@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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).