From: Scott Wood <scottwood@freescale.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, sam.mj@au1.ibm.com,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH 1/2] powerpc: Little endian should depend on PPC64
Date: Tue, 21 Apr 2015 13:33:03 -0500 [thread overview]
Message-ID: <1429641183.4352.108.camel@freescale.com> (raw)
In-Reply-To: <1429609312-32638-1-git-send-email-mpe@ellerman.id.au>
On Tue, 2015-04-21 at 19:41 +1000, Michael Ellerman wrote:
> The only little endian configuration we support is ppc64le, so we
> shouldn't be asking which endian to use when building 32-bit kernels,
> they are always big endian.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
> arch/powerpc/platforms/Kconfig.cputype | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/powerpc/platforms/Kconfig.cputype b/arch/powerpc/platforms/Kconfig.cputype
> index 7264e91190be..12fc443b9d54 100644
> --- a/arch/powerpc/platforms/Kconfig.cputype
> +++ b/arch/powerpc/platforms/Kconfig.cputype
> @@ -421,6 +421,7 @@ config CPU_BIG_ENDIAN
>
> config CPU_LITTLE_ENDIAN
> bool "Build little endian kernel"
> + depends on PPC64
> select PPC64_BOOT_WRAPPER
> help
> Build a little endian kernel.
Shouldn't this be PPC_BOOK3S_64?
-Scott
next prev parent reply other threads:[~2015-04-21 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 9:41 [PATCH 1/2] powerpc: Little endian should depend on PPC64 Michael Ellerman
2015-04-21 9:41 ` [PATCH 2/2] powerpc: Disable building the 32-bit VDSO on little endian Michael Ellerman
2015-04-21 18:36 ` Scott Wood
2015-04-22 0:30 ` Michael Ellerman
2015-04-21 22:23 ` Stephen Rothwell
2015-04-21 18:33 ` Scott Wood [this message]
2015-04-22 0:27 ` [PATCH 1/2] powerpc: Little endian should depend on PPC64 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=1429641183.4352.108.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sam.mj@au1.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.