From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/02] ARM: shmobile: romImage update
Date: Wed, 12 Jun 2013 14:09:29 +0000 [thread overview]
Message-ID: <20130612140928.GP32751@verge.net.au> (raw)
In-Reply-To: <20130605075514.17653.77135.sendpatchset@w520>
On Wed, Jun 05, 2013 at 04:55:14PM +0900, Magnus Damm wrote:
> ARM: shmobile: romImage update
>
> [PATCH 01/02] ARM: shmobile: Let romImage rely on default ATAGS
> [PATCH 02/02] ARM: shmobile: Remove romImage CONFIG_MEMORY_START
>
> Rework the mach-shmobile romImage code to remove memory configuration
> kept in the kernel configuration.
>
> This is one of several series of code that reworks code not to rely on
> CONFIG_MEMORY_START/SIZE which in turn is needed for ARCH_MULTIPLATFORM.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> Written against renesas.git renesas-next-20130604v2
>
> arch/arm/boot/compressed/head-shmobile.S | 21 ++-------------------
> arch/arm/mach-shmobile/include/mach/zboot.h | 2 ++
> 2 files changed, 4 insertions(+), 19 deletions(-)
Thanks, I have queued this up in the soc2 branch for v3.11.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/02] ARM: shmobile: romImage update
Date: Wed, 12 Jun 2013 23:09:29 +0900 [thread overview]
Message-ID: <20130612140928.GP32751@verge.net.au> (raw)
In-Reply-To: <20130605075514.17653.77135.sendpatchset@w520>
On Wed, Jun 05, 2013 at 04:55:14PM +0900, Magnus Damm wrote:
> ARM: shmobile: romImage update
>
> [PATCH 01/02] ARM: shmobile: Let romImage rely on default ATAGS
> [PATCH 02/02] ARM: shmobile: Remove romImage CONFIG_MEMORY_START
>
> Rework the mach-shmobile romImage code to remove memory configuration
> kept in the kernel configuration.
>
> This is one of several series of code that reworks code not to rely on
> CONFIG_MEMORY_START/SIZE which in turn is needed for ARCH_MULTIPLATFORM.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> Written against renesas.git renesas-next-20130604v2
>
> arch/arm/boot/compressed/head-shmobile.S | 21 ++-------------------
> arch/arm/mach-shmobile/include/mach/zboot.h | 2 ++
> 2 files changed, 4 insertions(+), 19 deletions(-)
Thanks, I have queued this up in the soc2 branch for v3.11.
next prev parent reply other threads:[~2013-06-12 14:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 7:55 [PATCH 00/02] ARM: shmobile: romImage update Magnus Damm
2013-06-05 7:55 ` Magnus Damm
2013-06-05 7:55 ` [PATCH 01/02] ARM: shmobile: Let romImage rely on default ATAGS Magnus Damm
2013-06-05 7:55 ` Magnus Damm
2013-06-05 11:51 ` Arnd Bergmann
2013-06-05 11:51 ` Arnd Bergmann
2013-06-06 3:13 ` Magnus Damm
2013-06-06 3:13 ` Magnus Damm
2013-06-06 16:19 ` Arnd Bergmann
2013-06-06 16:19 ` Arnd Bergmann
2013-06-07 0:14 ` Magnus Damm
2013-06-07 0:14 ` Magnus Damm
2013-06-12 14:10 ` Simon Horman
2013-06-12 14:10 ` Simon Horman
2013-06-05 7:55 ` [PATCH 02/02] ARM: shmobile: Remove romImage CONFIG_MEMORY_START Magnus Damm
2013-06-05 7:55 ` Magnus Damm
2013-06-12 14:10 ` Simon Horman
2013-06-12 14:10 ` Simon Horman
2013-06-12 14:09 ` Simon Horman [this message]
2013-06-12 14:09 ` [PATCH 00/02] ARM: shmobile: romImage update Simon Horman
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=20130612140928.GP32751@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.