From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: malat@debian.org, rdunlap@infradead.org, npiggin@gmail.com
Subject: Re: [1/2] powerpc: Add ppc32_allmodconfig defconfig target
Date: Tue, 24 Jul 2018 23:59:54 +1000 (AEST) [thread overview]
Message-ID: <41Zg3G6V47z9s55@ozlabs.org> (raw)
In-Reply-To: <20180709142426.26999-1-mpe@ellerman.id.au>
On Mon, 2018-07-09 at 14:24:25 UTC, Michael Ellerman wrote:
> Because the allmodconfig logic just sets every symbol to M or Y, it
> has the effect of always generating a 64-bit config, because
> CONFIG_PPC64 becomes Y.
>
> So to make it easier for folks to test 32-bit code, provide a phony
> defconfig target that generates a 32-bit allmodconfig.
>
> The 32-bit port has several mutually exclusive CPU types, we choose
> the Book3S variants as that's what the help text in Kconfig says is
> most common.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Series applied to powerpc next.
https://git.kernel.org/powerpc/c/8db0c9d416f26018cb7cabfb0b144f
cheers
prev parent reply other threads:[~2018-07-24 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 14:24 [PATCH 1/2] powerpc: Add ppc32_allmodconfig defconfig target Michael Ellerman
2018-07-09 14:24 ` [PATCH 2/2] powerpc: Add ppc64le and ppc64_book3e allmodconfig targets Michael Ellerman
2018-07-15 19:40 ` Randy Dunlap
2018-07-20 11:51 ` Michael Ellerman
2018-07-10 7:58 ` [PATCH 1/2] powerpc: Add ppc32_allmodconfig defconfig target Mathieu Malaterre
2018-07-10 13:47 ` Michael Ellerman
2018-07-11 7:09 ` Mathieu Malaterre
2018-07-11 13:50 ` Michael Ellerman
2018-07-14 1:59 ` Randy Dunlap
2018-07-20 11:58 ` Michael Ellerman
2018-07-14 4:35 ` Randy Dunlap
2018-07-20 12:18 ` Michael Ellerman
2018-07-24 13:59 ` Michael Ellerman [this message]
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=41Zg3G6V47z9s55@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=malat@debian.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rdunlap@infradead.org \
/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).