From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@linux-foundation.org>, Helge Deller <deller@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
Michael Kerrisk <mtk.manpages@googlemail.com>,
linux-api@vger.kernel.org
Subject: Re: [PATCH] prctl: implement PR_GET_ENDIAN for all architectures
Date: Wed, 01 Feb 2017 15:12:12 -0800 [thread overview]
Message-ID: <1485990732.2322.40.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170131162624.5a85ec47c6ee22e5cc03c4eb@linux-foundation.org>
On Tue, 2017-01-31 at 16:26 -0800, Andrew Morton wrote:
> On Sat, 28 Jan 2017 12:13:10 +0100 Helge Deller <deller@gmx.de>
> wrote:
>
> > The prctl(PR_GET_ENDIAN) syscall was added to Kernel 2.6.18, but
> > implemented for PowerPC only. This trivial patch adds support for
> > this syscall for all other architectures.
>
> Seems reasonable. I guess. Why is this needed?
I don't think it is other than for PPC. If you're not variable endian
(which is only PPC to date), then you should know a priori what endian
you are from the #defines in userspace.
James
next prev parent reply other threads:[~2017-02-01 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170128111310.GA13389@ls3530.fritz.box>
2017-02-01 0:26 ` [PATCH] prctl: implement PR_GET_ENDIAN for all architectures Andrew Morton
[not found] ` <20170131162624.5a85ec47c6ee22e5cc03c4eb-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2017-02-01 19:47 ` Helge Deller
[not found] ` <7c60f97a-4b63-5eff-e837-186f9a31c5a2-Mmb7MZpHnFY@public.gmane.org>
2017-02-01 22:03 ` Andrew Morton
2017-02-01 23:12 ` James Bottomley [this message]
2017-02-02 5:08 ` Andy Lutomirski
2017-02-05 11:48 ` Matt Turner
2017-02-05 13:15 ` Maciej W. Rozycki
2017-02-15 5:20 ` Michael Ellerman
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=1485990732.2322.40.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=deller@gmx.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
/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).