From: "H. Peter Anvin" <hpa@zytor.com>
To: Helge Deller <deller@gmx.de>
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>,
John David Anglin <dave.anglin@bell.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Rolf Eike Beer <eike-kernel@sf-tec.de>,
Ian Kent <raven@themaw.net>,
autofs@vger.kernel.org
Subject: Re: [PATCH] unbreak automounter support on 64-bit kernel with 32-bit userspace (v2)
Date: Mon, 04 Feb 2013 13:35:38 -0800 [thread overview]
Message-ID: <511029AA.1060007@zytor.com> (raw)
In-Reply-To: <20130204193952.GA5785@p100.box>
On 02/04/2013 11:39 AM, Helge Deller wrote:
>
> This suggestion is probably the best way to go, since Arm64 (and maybe others?)
> seems to have a non-working automounter. So in the long run even for other new
> upcoming architectures this inverted check seem to be the best solution, since
> it will not require them to change this #if again (unless they are 64bit only).
>
... and even then they will generally work just fine.
-hpa
next prev parent reply other threads:[~2013-02-04 21:35 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
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 [this message]
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=511029AA.1060007@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=autofs@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=eike-kernel@sf-tec.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