From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-kernel@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Andrew Victor <linux@maxim.org.za>
Subject: Re: [PATCH] ARM: at91: force CPU selection
Date: Fri, 13 Mar 2015 21:30:56 +0100 [thread overview]
Message-ID: <20150313203056.GL4329@piout.net> (raw)
In-Reply-To: <6645156.Abd4ZAJv10@wuerfel>
On 13/03/2015 at 20:50:59 +0100, Arnd Bergmann wrote :
> >
> > Actually, I had a closer look today and there is already just one level
> > in my current version of patches.
> >
> > I can put everything under menuconfig ARCH_AT91 but I can't remove
> > SOC_SAM_V7 and SOC_SAM_V4_V5 because that is what is used to select
> > which dtb should be compiled.
> >
> > This would also break sama5_defconfig. This is a simple fix but that
> > means that it makes it difficult to migrate an existing .config.
> >
> > I'd say let's keep it that way as this is not broken, unless you really
> > want to see SOC_SAM_V7 and SOC_SAM_V4_V5 being removed.
> >
>
> I'm not sure what the latest version looks like, but I think it's fine
> to have SOC_SAM_V4_V5 automatically selected when CONFIG_AT91 and
> CONFIG_MULTI_V4 || CONFIG_MULTI_V5 are turned on, or selected by
> AT91SAM9 and AT91RM9200.
>
OK, I'm doing that. I'll send v3 in a few minutes.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-13 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 6:59 [PATCH] ARM: at91: force CPU selection Brian Norris
2015-03-10 9:02 ` Arnd Bergmann
2015-03-10 9:42 ` Alexandre Belloni
2015-03-10 13:42 ` Arnd Bergmann
2015-03-13 18:32 ` Alexandre Belloni
2015-03-13 19:50 ` Arnd Bergmann
2015-03-13 20:30 ` Alexandre Belloni [this message]
2015-03-10 20:02 ` Brian Norris
2015-03-10 21:13 ` Alexandre Belloni
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=20150313203056.GL4329@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=computersforpeace@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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).