From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [RESEND PATCH net-next-2.6 3/3] ipv6 sit: Set relay to 0.0.0.0 directly if relay_prefixlen == 0.
Date: Mon, 12 Oct 2009 02:08:06 -0700 (PDT) [thread overview]
Message-ID: <20091012.020806.98275364.davem@davemloft.net> (raw)
In-Reply-To: <1255337454.2878.7.camel@cirrhata.linux-ipv6.org>
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Date: Mon, 12 Oct 2009 17:50:54 +0900
> Unfortunately, on x86 architecture (80286 and later at least),
> lower 5 bits (& 0x1f) are used for shift operation.
> Thus, 0xffffffffUL << 32 gives 0xffffffffUL.
Indeed, thanks for the explanation, I thought only right
shift mattered for this case of "shift count larger than
type".
next prev parent reply other threads:[~2009-10-12 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 13:45 [RESEND PATCH net-next-2.6 3/3] ipv6 sit: Set relay to 0.0.0.0 directly if relay_prefixlen == 0 YOSHIFUJI Hideaki
2009-10-12 7:32 ` Eric Dumazet
2009-10-12 8:18 ` David Miller
2009-10-12 9:03 ` YOSHIFUJI Hideaki
2009-10-12 8:50 ` YOSHIFUJI Hideaki
2009-10-12 9:08 ` David Miller [this message]
2009-10-12 9:08 ` David Miller
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=20091012.020806.98275364.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--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).