From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/04] ARM: shmobile: KZM9D legacy board code removal
Date: Fri, 08 Nov 2013 07:52:37 +0000 [thread overview]
Message-ID: <20131108075235.GD23477@verge.net.au> (raw)
In-Reply-To: <20131106232102.8081.20523.sendpatchset@w520>
On Thu, Nov 07, 2013 at 08:21:02AM +0900, Magnus Damm wrote:
> ARM: shmobile: KZM9D legacy board code removal
>
> [PATCH 01/04] ARM: shmobile: Add shared EMEV2 code for ->init_machine()
> [PATCH 02/04] ARM: shmobile: Use ->init_late() in shared EMEV2 case
> [PATCH 03/04] ARM: shmobile: Remove legacy KZM9D board code
> [PATCH 04/04] ARM: shmobile: Remove legacy platform devices from EMEV2 SoC code
>
> With this patch set applied it is possible to use DT for KZM9D board support.
> Because of this is the KZM9D legacy C board code removed together with EMEV2
> platform devices. All these devices are available via DT anyway, so there is
> no need to keep the C version. This saves some lines of code and shows where
> mach-shmobile is heading in the future for all the SoCs.
Thanks, I have queued these up.
prev parent reply other threads:[~2013-11-08 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 23:21 [PATCH 00/04] ARM: shmobile: KZM9D legacy board code removal Magnus Damm
2013-11-06 23:21 ` [PATCH 01/04] ARM: shmobile: Add shared EMEV2 code for ->init_machine() Magnus Damm
2013-11-06 23:21 ` [PATCH 02/04] ARM: shmobile: Use ->init_late() in shared EMEV2 case Magnus Damm
2013-11-06 23:21 ` [PATCH 03/04] ARM: shmobile: Remove legacy KZM9D board code Magnus Damm
2013-11-08 8:49 ` Simon Horman
2013-11-08 10:03 ` Magnus Damm
2013-11-08 23:34 ` Simon Horman
2013-11-06 23:21 ` [PATCH 04/04] ARM: shmobile: Remove legacy platform devices from EMEV2 SoC code Magnus Damm
2013-11-08 7:52 ` Simon Horman [this message]
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=20131108075235.GD23477@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 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).