From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: at91: force CPU selection
Date: Tue, 10 Mar 2015 22:13:43 +0100 [thread overview]
Message-ID: <20150310211343.GI9188@piout.net> (raw)
In-Reply-To: <20150310200209.GE4124@norris-Latitude-E6410>
On 10/03/2015 at 13:02:09 -0700, Brian Norris wrote :
> On Tue, Mar 10, 2015 at 10:02:15AM +0100, Arnd Bergmann wrote:
> > I actually added a bunch of these in other places, but have stopped
> > doing so because Russell didn't like them, and I tend to follow
> > his argument now that it's actually pretty confusing.
>
> I'm not a big fan of my patch, but it did at least solve the problem.
> Thanks for the info, and I'm happy to drop my patch. At least I've fixed
> my compile-test setups to avoid bad combinations, now.
>
> To be clear, multiplatform support is in progress, but not merged yet,
> right?
>
I can point you to the patch series if you want. Hopefully, this will be
merged for 4.1
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-kernel@vger.kernel.org,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Andrew Victor <linux@maxim.org.za>
Subject: Re: [PATCH] ARM: at91: force CPU selection
Date: Tue, 10 Mar 2015 22:13:43 +0100 [thread overview]
Message-ID: <20150310211343.GI9188@piout.net> (raw)
In-Reply-To: <20150310200209.GE4124@norris-Latitude-E6410>
On 10/03/2015 at 13:02:09 -0700, Brian Norris wrote :
> On Tue, Mar 10, 2015 at 10:02:15AM +0100, Arnd Bergmann wrote:
> > I actually added a bunch of these in other places, but have stopped
> > doing so because Russell didn't like them, and I tend to follow
> > his argument now that it's actually pretty confusing.
>
> I'm not a big fan of my patch, but it did at least solve the problem.
> Thanks for the info, and I'm happy to drop my patch. At least I've fixed
> my compile-test setups to avoid bad combinations, now.
>
> To be clear, multiplatform support is in progress, but not merged yet,
> right?
>
I can point you to the patch series if you want. Hopefully, this will be
merged for 4.1
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-10 21:13 UTC|newest]
Thread overview: 18+ 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 6:59 ` Brian Norris
2015-03-10 9:02 ` Arnd Bergmann
2015-03-10 9:02 ` Arnd Bergmann
2015-03-10 9:42 ` Alexandre Belloni
2015-03-10 9:42 ` Alexandre Belloni
2015-03-10 13:42 ` Arnd Bergmann
2015-03-10 13:42 ` Arnd Bergmann
2015-03-13 18:32 ` Alexandre Belloni
2015-03-13 18:32 ` Alexandre Belloni
2015-03-13 19:50 ` Arnd Bergmann
2015-03-13 19:50 ` Arnd Bergmann
2015-03-13 20:30 ` Alexandre Belloni
2015-03-13 20:30 ` Alexandre Belloni
2015-03-10 20:02 ` Brian Norris
2015-03-10 20:02 ` Brian Norris
2015-03-10 21:13 ` Alexandre Belloni [this message]
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=20150310211343.GI9188@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=linux-arm-kernel@lists.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 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.