From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 02/04] ARM: shmobile: Introduce ARCH_SHMOBILE_MULTI
Date: Tue, 23 Jul 2013 01:24:45 +0000 [thread overview]
Message-ID: <20130723012444.GD16481@verge.net.au> (raw)
In-Reply-To: <20130717203109.27542.77708.sendpatchset@w520>
On Thu, Jul 18, 2013 at 05:31:09AM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> Add ARCH_SHMOBILE_MULTI to mach-shmobile that can be used
> to enable ARCH_MULTIPLATFORM on selected SoCs and boards.
>
> The headers stay under arch/arm/mach-shmobile/include/mach/
> for now, they can and will be migrated independently over time.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> arch/arm/Makefile | 1 +
> arch/arm/mach-shmobile/Kconfig | 21 +++++++++++++++++++++
> arch/arm/mach-shmobile/Makefile | 2 ++
> 3 files changed, 24 insertions(+)
Thanks, I have queued this up for v3.12 in a new multiarch branch
of the renesas tree.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/04] ARM: shmobile: Introduce ARCH_SHMOBILE_MULTI
Date: Tue, 23 Jul 2013 10:24:45 +0900 [thread overview]
Message-ID: <20130723012444.GD16481@verge.net.au> (raw)
In-Reply-To: <20130717203109.27542.77708.sendpatchset@w520>
On Thu, Jul 18, 2013 at 05:31:09AM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> Add ARCH_SHMOBILE_MULTI to mach-shmobile that can be used
> to enable ARCH_MULTIPLATFORM on selected SoCs and boards.
>
> The headers stay under arch/arm/mach-shmobile/include/mach/
> for now, they can and will be migrated independently over time.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> arch/arm/Makefile | 1 +
> arch/arm/mach-shmobile/Kconfig | 21 +++++++++++++++++++++
> arch/arm/mach-shmobile/Makefile | 2 ++
> 3 files changed, 24 insertions(+)
Thanks, I have queued this up for v3.12 in a new multiarch branch
of the renesas tree.
next prev parent reply other threads:[~2013-07-23 1:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 20:30 [PATCH v2 00/04] ARM: shmobile: ARCH_MULTIPLATFORM for EMEV2 and KZM9D Magnus Damm
2013-07-17 20:30 ` Magnus Damm
2013-07-17 20:30 ` [PATCH v2 01/04] ARM: shmobile: Only build clocks when COMMON_CLK=n Magnus Damm
2013-07-17 20:30 ` Magnus Damm
2013-07-23 1:24 ` Simon Horman
2013-07-23 1:24 ` Simon Horman
2013-07-17 20:31 ` [PATCH 02/04] ARM: shmobile: Introduce ARCH_SHMOBILE_MULTI Magnus Damm
2013-07-17 20:31 ` Magnus Damm
2013-07-23 1:24 ` Simon Horman [this message]
2013-07-23 1:24 ` Simon Horman
2013-07-17 20:31 ` [PATCH v2 03/04] ARM: shmobile: Add EMEV2 and KZM9D to ARCH_SHMOBILE_MULTI Magnus Damm
2013-07-17 20:31 ` Magnus Damm
2013-07-23 1:24 ` Simon Horman
2013-07-23 1:24 ` Simon Horman
2013-07-17 20:31 ` [PATCH 04/04] ARM: shmobile: Allow ARCH_SHMOBILE_MULTI timer configuration Magnus Damm
2013-07-17 20:31 ` Magnus Damm
2013-07-23 1:24 ` Simon Horman
2013-07-23 1:24 ` Simon Horman
2013-07-19 2:28 ` [PATCH v2 00/04] ARM: shmobile: ARCH_MULTIPLATFORM for EMEV2 and KZM9D Simon Horman
2013-07-19 2:28 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2013-07-09 5:43 [PATCH " Magnus Damm
2013-07-09 5:43 ` [PATCH 02/04] ARM: shmobile: Introduce ARCH_SHMOBILE_MULTI Magnus Damm
2013-07-09 5:43 ` Magnus Damm
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=20130723012444.GD16481@verge.net.au \
--to=horms@verge.net.au \
--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.