From: "David S. Miller" <davem@redhat.com>
To: Dan Merillat <dmerillat@sequiam.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Nasty Oops in 2.6.0-test6 bind/SO_REUSEADDR
Date: Wed, 8 Oct 2003 13:34:25 -0700 [thread overview]
Message-ID: <20031008133425.518432fe.davem@redhat.com> (raw)
In-Reply-To: <20031008200409.GA2514@chaos.ao.net>
I've forwarded your report to netdev@oss.sgi.com, please send
networking bug reports there in the future since that is where
the networking developers live, not here. Thanks.
prev parent reply other threads:[~2003-10-08 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 20:04 Nasty Oops in 2.6.0-test6 bind/SO_REUSEADDR Dan Merillat
2003-10-08 20:34 ` 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=20031008133425.518432fe.davem@redhat.com \
--to=davem@redhat.com \
--cc=dmerillat@sequiam.com \
--cc=linux-kernel@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