From: Andi Kleen <andi@firstfloor.org>
To: David Miller <davem@davemloft.net>
Cc: john.dykstra1@gmail.com, mailinglists+netdev@oliverzheng.com,
netdev@vger.kernel.org, andi@firstfloor.org
Subject: Re: [PATCH net-next-2.6] Re: TCP/IP stack interpretation of acceptable packet
Date: Mon, 23 Mar 2009 13:28:06 +0100 [thread overview]
Message-ID: <20090323122806.GA11935@one.firstfloor.org> (raw)
In-Reply-To: <20090322.215033.192091282.davem@davemloft.net>
> I've been mulling over this patch for more than a week :-)
>
> Let's put this into net-next-2.6 and let it cook there for
> a while. It is possible I'll backport this into -stable
> after some time.
One thing that might be useful for the testing period would
be explicit printk when such a new discard happens? Otherwise
it would be difficult to find out if something really goes wrong.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-03-23 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 22:59 TCP/IP stack interpretation of acceptable packet Oliver Zheng
2009-02-28 15:50 ` Andi Kleen
2009-03-19 0:44 ` [PATCH net-next-2.6] " John Dykstra
2009-03-19 1:47 ` Oliver Zheng
2009-03-23 4:50 ` David Miller
2009-03-23 12:28 ` Andi Kleen [this message]
2009-03-23 15:13 ` John Dykstra
2009-03-23 18:58 ` 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=20090323122806.GA11935@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=john.dykstra1@gmail.com \
--cc=mailinglists+netdev@oliverzheng.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).