From: Rob Landley <rob@landley.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Joe Perches <joe@perches.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-arch <linux-arch@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
james.t.kukunas@intel.com, David Miller <davem@davemloft.net>
Subject: Re: [tip:x86/asm] x86, bitops: Change bitops to be native operand size
Date: Sat, 30 Nov 2013 17:16:22 -0600 [thread overview]
Message-ID: <1385853382.1974.297@driftwood> (raw)
In-Reply-To: <CAMuHMdWxRsiFGNBSsoEhyusyDWhuTQS+ecUiPHH1Yaufj43X1g@mail.gmail.com> (from geert@linux-m68k.org on Tue Nov 12 02:52:57 2013)
On 11/12/2013 02:52:57 AM, Geert Uytterhoeven wrote:
> On Tue, Nov 12, 2013 at 5:08 AM, Joe Perches <joe@perches.com> wrote:
> > On Tue, 2013-11-12 at 12:15 +0900, Linus Torvalds wrote:
> >> Talking about "ideal implementation" is also singularly stupid.
> >
> > I just want the various arch implementations to match
> > the docs. I know that's stupid.
> >
> > Maybe if you really don't want to discuss things, you
> > should fix the documentation.
>
> E.g. by adding a paragraph that the actual allowed range of indices
> may be
> a subset of "unsigned long" on some architectures.
> Or if we know that everyone supports at least 31 resp. 63 bits, that
> it may
> be limited to 31 resp. 63 unsigned bits, which is the positive range
> subset of
> "long".
If this ever turns into an actual patch to this file, could you cc: me
on it so I can marshal it upstream? (Not enough domain expertise for me
to produce it myself...)
Thanks,
Rob
prev parent reply other threads:[~2013-12-01 2:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 1:15 [tip:x86/asm] x86, bitops: Change bitops to be native operand size tip-bot for H. Peter Anvin
2013-11-10 21:09 ` Joe Perches
2013-11-10 22:10 ` H. Peter Anvin
2013-11-10 22:44 ` Joe Perches
2013-11-11 2:06 ` H. Peter Anvin
2013-11-11 2:22 ` Joe Perches
2013-11-11 23:34 ` H. Peter Anvin
2013-11-12 2:54 ` Joe Perches
2013-11-12 3:15 ` Linus Torvalds
2013-11-12 4:08 ` Joe Perches
2013-11-12 8:52 ` Geert Uytterhoeven
2013-11-30 23:16 ` Rob Landley [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=1385853382.1974.297@driftwood \
--to=rob@landley.net \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=james.t.kukunas@intel.com \
--cc=joe@perches.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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