From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: 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 15:39:53 -0800 [thread overview]
Message-ID: <20040129153953.3dd2cd23.davem@redhat.com> (raw)
In-Reply-To: <20040130.083743.20740540.yoshfuji@linux-ipv6.org>
On Fri, 30 Jan 2004 08:37:43 +0900 (JST)
YOSHIFUJI Hideaki / ^[$B5HF#1QL@^[(B <yoshfuji@linux-ipv6.org> wrote:
> For long term solution, I think it is better to store timing variables
> in "unsinged long" type instead of int.
I think this is the only fix to even consider, even in the short term.
The macro suggested is just too much of a hack. :)
We can just ignore the silly warning until we are able to find time
to do the correct fix.
next prev parent reply other threads:[~2004-01-29 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 21:15 Patch: IPv6/AMD64: bug in net/ipv6/ndisc.c Jan Kasprzak
2004-01-29 23:37 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-29 23:39 ` David S. Miller [this message]
2004-01-30 0:40 ` Andi Kleen
2004-01-30 0:56 ` David S. Miller
2004-01-30 1:07 ` Andi Kleen
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=20040129153953.3dd2cd23.davem@redhat.com \
--to=davem@redhat.com \
--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