From: "David S. Miller" <davem@redhat.com>
To: "Wesley W. Terpstra" <terpstra@gkec.tu-darmstadt.de>
Cc: yoshfuji@linux-ipv6.org, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: Broken? 2.6.6 + IP_ADD_SOURCE_MEMBERSHIP + SO_REUSEADDR
Date: Fri, 4 Jun 2004 14:29:28 -0700 [thread overview]
Message-ID: <20040604142928.0d9045ce.davem@redhat.com> (raw)
In-Reply-To: <20040604212916.GA6683@muffin>
On Fri, 4 Jun 2004 23:29:16 +0200
"Wesley W. Terpstra" <terpstra@gkec.tu-darmstadt.de> wrote:
> I am amazed you fixed it so fast!
> Will this make it into 2.6.7?
Yes, and 2.4.27 hopefully as well.
next prev parent reply other threads:[~2004-06-04 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040604155423.GA5656@muffin>
2004-06-04 16:55 ` Broken? 2.6.6 + IP_ADD_SOURCE_MEMBERSHIP + SO_REUSEADDR YOSHIFUJI Hideaki / 吉藤英明
2004-06-04 17:14 ` YOSHIFUJI Hideaki / 吉藤英明
2004-06-04 21:00 ` David S. Miller
2004-06-04 21:29 ` Wesley W. Terpstra
2004-06-04 21:29 ` David S. Miller [this message]
2004-06-04 15:54 Wesley W. Terpstra
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=20040604142928.0d9045ce.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=terpstra@gkec.tu-darmstadt.de \
--cc=yoshfuji@linux-ipv6.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).