From: "David S. Miller" <davem@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: yoshfuji@linux-ipv6.org, kas@informatics.muni.cz,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Patch: IPv6/AMD64: bug in net/ipv6/ndisc.c
Date: Thu, 29 Jan 2004 16:56:45 -0800 [thread overview]
Message-ID: <20040129165645.4dde4ffc.davem@redhat.com> (raw)
In-Reply-To: <20040130014031.31ec050f.ak@suse.de>
On Fri, 30 Jan 2004 01:40:31 +0100
Andi Kleen <ak@suse.de> wrote:
> Fine by me. I've been ignoring it forever. But don't you see it on sparc64 too?
Nope, for some reason gcc-3.2.3 on my systems is missing it.
Otherwise I would have killed this earlier :)
next prev parent reply other threads:[~2004-01-30 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040129221538.J24747@fi.muni.cz>
2004-01-29 23:37 ` Patch: IPv6/AMD64: bug in net/ipv6/ndisc.c YOSHIFUJI Hideaki / 吉藤英明
2004-01-29 23:39 ` David S. Miller
2004-01-30 0:40 ` Andi Kleen
2004-01-30 0:56 ` David S. Miller [this message]
2004-01-30 1:07 ` Andi Kleen
2004-01-29 21:15 Jan Kasprzak
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=20040129165645.4dde4ffc.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@suse.de \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--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).