From: "H. Peter Anvin" <hpa@zytor.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use __kernel_long_t in struct mq_attr
Date: Thu, 26 Dec 2013 10:03:37 -0800 [thread overview]
Message-ID: <52BC6F79.7040006@zytor.com> (raw)
In-Reply-To: <CAMe9rOoS4qMmTyyHvv2xq1zyFuKFk=++kfx7mM_CGhS-b8fTkA@mail.gmail.com>
On 12/26/2013 09:59 AM, H.J. Lu wrote:
>
>> but it would seem to give the wrong types when __BITS_PER_LONG in
>> userspace is 32.
>>
>
> For x32, __BITS_PER_LONG is 64, not 32. If __BITS_PER_LONG
> is 32, my patch doesn't change anything. If it works before,
> it still works. If it is broken before, it remains broken.
>
> I prefer my first patch, which is less clutter. But I can't guarantee
> it is correct for all x3-like ABIs. My second patch has more
> clutter, but it has no impact on other ABIs.
>
It's rather simple to prove, which is to consider the generic definition
of __kernel_[u]long_t.
-hpa
next prev parent reply other threads:[~2013-12-26 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 16:58 [PATCH] Use __kernel_long_t in struct mq_attr H.J. Lu
2013-12-26 15:54 ` H.J. Lu
2013-12-26 17:53 ` H. Peter Anvin
2013-12-26 17:59 ` H.J. Lu
2013-12-26 18:03 ` H. Peter Anvin [this message]
2013-12-26 18:10 ` H.J. Lu
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=52BC6F79.7040006@zytor.com \
--to=hpa@zytor.com \
--cc=hjl.tools@gmail.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