From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: multiplatform for 4.1 #1
Date: Thu, 02 Apr 2015 16:17:49 +0200 [thread overview]
Message-ID: <4695444.mEPNvRWLFJ@wuerfel> (raw)
In-Reply-To: <1426785269-6484-1-git-send-email-nicolas.ferre@atmel.com>
On Thursday 19 March 2015 18:14:29 Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> This is the real switch to multi-platform for AT91: after all the preparation
> work that has been done, here we are! And there's also an additional cleanup on
> top of that...
> I stacked this material on top of my previous "at91-cleanup3" tag that I had sent
> you earlier this week. As all my cleanup material is also on top of the fixes
> tags (that you already have), these patches are also adapted to match this
> state and avoid conflicts.
> So, you can have this tag in your "multiplatform" branch separated, like I did,
> or simply stacked on top or the AT91 cleanup material.
I got a build error with legacy (non-multi) platforms when ARCH_AT91 is enabled
and needed this change on top:
diff --git a/arch/arm/mach-at91/Kconfig b/arch/arm/mach-at91/Kconfig
index e2cd30f6c23d..fd95f34945f4 100644
--- a/arch/arm/mach-at91/Kconfig
+++ b/arch/arm/mach-at91/Kconfig
@@ -1,5 +1,6 @@
menuconfig ARCH_AT91
bool "Atmel SoCs"
+ depends on ARCH_MULTI_V4T || ARCH_MULTI_V5 || ARCH_MULTI_V7
select ARCH_REQUIRE_GPIOLIB
select COMMON_CLK_AT91
select PINCTRL
Can you check if that is the right approach and submit it as a proper
patch?
Arnd
next prev parent reply other threads:[~2015-04-02 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 17:14 [GIT PULL] at91: multiplatform for 4.1 #1 Nicolas Ferre
2015-04-02 0:59 ` Olof Johansson
2015-04-02 14:17 ` Arnd Bergmann [this message]
2015-04-02 15:07 ` [PATCH] ARM: at91: add a Kconfig dependency on multi-platform Nicolas Ferre
2015-04-03 17:47 ` Olof Johansson
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=4695444.mEPNvRWLFJ@wuerfel \
--to=arnd@arndb.de \
--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 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).