From: "David S. Miller" <davem@davemloft.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH 2.6]: keep fragment queues private to each user
Date: Wed, 26 Jan 2005 22:29:55 -0800 [thread overview]
Message-ID: <20050126222955.729c390b.davem@davemloft.net> (raw)
In-Reply-To: <41F82830.9010009@trash.net>
On Thu, 27 Jan 2005 00:30:56 +0100
Patrick McHardy <kaber@trash.net> wrote:
> Sorry, new patch attached. I'll send the 2.4 patch later tonight.
Thanks. I'll apply this and the 2.4.x variant.
Although I have a theoretical objection to this thing. It is
extending a namespace we have no such control over. The namespace
is saddr/daddr/ID. But perhaps I'm being overly anal.
prev parent reply other threads:[~2005-01-27 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 4:57 [PATCH 2.6]: keep fragment queues private to each user Patrick McHardy
2005-01-25 11:57 ` Herbert Xu
2005-01-25 14:41 ` Patrick McHardy
2005-01-25 20:47 ` Herbert Xu
2005-01-26 5:41 ` David S. Miller
2005-01-26 23:30 ` Patrick McHardy
2005-01-27 2:44 ` [PATCH 2.4]: " Patrick McHardy
2005-01-27 6:29 ` David S. Miller [this message]
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=20050126222955.729c390b.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.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).