From: Cyril Bur <cyrilbur@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/configs: Add a powernv_be_defconfig
Date: Fri, 28 Jul 2017 16:13:18 +1000 [thread overview]
Message-ID: <1501222398.3324.7.camel@gmail.com> (raw)
In-Reply-To: <1500900645-12237-1-git-send-email-mpe@ellerman.id.au>
On Mon, 2017-07-24 at 22:50 +1000, Michael Ellerman wrote:
> Although pretty much everyone using powernv is running little endian,
> we should still test we can build for big endian. So add a
> powernv_be_defconfig, which is autogenerated by flipping the endian
> symbol in powernv_defconfig.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Reviewed-by: Cyril Bur <cyrilbur@gmail.com>
> ---
> arch/powerpc/Makefile | 4 ++++
> arch/powerpc/configs/be.config | 1 +
> 2 files changed, 5 insertions(+)
> create mode 100644 arch/powerpc/configs/be.config
>
> diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
> index 8d4ed73d5490..7b8eddfc46d2 100644
> --- a/arch/powerpc/Makefile
> +++ b/arch/powerpc/Makefile
> @@ -316,6 +316,10 @@ PHONY += ppc64le_defconfig
> ppc64le_defconfig:
> $(call merge_into_defconfig,ppc64_defconfig,le)
>
> +PHONY += powernv_be_defconfig
> +powernv_be_defconfig:
> + $(call merge_into_defconfig,powernv_defconfig,be)
> +
> PHONY += mpc85xx_defconfig
> mpc85xx_defconfig:
> $(call merge_into_defconfig,mpc85xx_basic_defconfig,\
> diff --git a/arch/powerpc/configs/be.config b/arch/powerpc/configs/be.config
> new file mode 100644
> index 000000000000..c5cdc99a6530
> --- /dev/null
> +++ b/arch/powerpc/configs/be.config
> @@ -0,0 +1 @@
> +CONFIG_CPU_BIG_ENDIAN=y
next prev parent reply other threads:[~2017-07-28 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 12:50 [PATCH] powerpc/configs: Add a powernv_be_defconfig Michael Ellerman
2017-07-28 6:13 ` Cyril Bur [this message]
2017-08-07 10:41 ` 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=1501222398.3324.7.camel@gmail.com \
--to=cyrilbur@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).