From: "H. Peter Anvin" <hpa@zytor.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
Ian Kent <raven@themaw.net>,
autofs@vger.kernel.org
Subject: Re: [PATCH] parisc: unbreak automounter support on 64-bit kernel with 32-bit userspace
Date: Thu, 31 Jan 2013 13:46:11 -0800 [thread overview]
Message-ID: <510AE623.7000609@zytor.com> (raw)
In-Reply-To: <1359668524.2468.12.camel@dabdike>
On 01/31/2013 01:42 PM, James Bottomley wrote:
> On Thu, 2013-01-31 at 13:29 -0800, H. Peter Anvin wrote:
>> On 01/31/2013 12:26 PM, James Bottomley wrote:
>>> [adding autofs list and maintainer for their perusal and ack, although
>>> this is an obvious fix to me
>>>
>>> James]
>>
>> The #if list probably should be inverted, and only specific platforms
>> should have unsigned long...
>
> The whitelist is 64 bit only platforms, like ia64, isn't it? So yes,
> they're far less numerous.
>
Correct. It is basically the 64-bit platforms without any 32-bit
userspace, like Alpha and IA64.
-hpa
next prev parent reply other threads:[~2013-01-31 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 20:01 [PATCH] parisc: unbreak automounter support on 64-bit kernel with 32-bit userspace Helge Deller
2013-01-31 20:26 ` James Bottomley
2013-01-31 21:00 ` Rolf Eike Beer
2013-01-31 21:29 ` H. Peter Anvin
2013-01-31 21:42 ` James Bottomley
2013-01-31 21:46 ` H. Peter Anvin [this message]
2013-01-31 22:10 ` Rolf Eike Beer
2013-01-31 23:13 ` H. Peter Anvin
2013-02-01 14:51 ` Catalin Marinas
2013-02-04 19:39 ` [PATCH] unbreak automounter support on 64-bit kernel with 32-bit userspace (v2) Helge Deller
2013-02-04 21:35 ` H. Peter Anvin
2013-02-06 5:58 ` Ian Kent
2013-02-06 17:08 ` H. Peter Anvin
2013-02-06 17:21 ` Catalin Marinas
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=510AE623.7000609@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=autofs@vger.kernel.org \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=raven@themaw.net \
/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).