From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: shmobile: sh73a0/kzm9g: Introduce multiplatform support
Date: Fri, 23 Jan 2015 13:22:56 +0900 [thread overview]
Message-ID: <20150123042255.GC17548@verge.net.au> (raw)
In-Reply-To: <20150122025002.GA12687@verge.net.au>
On Thu, Jan 22, 2015 at 11:50:03AM +0900, Simon Horman wrote:
> On Thu, Jan 22, 2015 at 11:48:05AM +0900, Simon Horman wrote:
> > On Tue, Jan 13, 2015 at 11:08:14AM +0900, Simon Horman wrote:
> > > On Fri, Jan 09, 2015 at 02:08:48PM +0100, Geert Uytterhoeven wrote:
> > > > Hi Simon, Magnus,
> > > >
> > > > This patch series (by Magnus) introduces multiplatform support for the
> > > > sh73a0 platform. After this kzm9g can boot a sh73a0 multiplatform
> > > > kernel fine, except for working Ethernet (the ZB clock is disabled by
> > > > clk_disable_unused()).
> > > >
> > > > This series has been sent before by Magnus as part of the series
> > > > "[PATCH v2 00/05] ARM: shmobile: sh73a0 and kzm9g Multiplatform
> > > > revisit" (http://www.spinics.net/lists/linux-sh/msg38384.html).
> > > > I've updated the kzm9g DTS sync patch for recent changes to the
> > > > kzm9g-reference DTS.
> > > >
> > > > Thanks for applying!
> > >
> > > Thanks, done.
> >
> > For the record: Olof has asked for review comments for the BSC driver
> > and binding patches. Accordingly I have dropped them, and these patches
> > which depend on them, from next.
>
> To clarify, this dependency may be due to the way the branches are arranged,
> rather than actual dependencies of the code. But regardless I am dropping
> all effected branches for now.
I have now had a chance to re-examine these patches and it seems to me that
they do not depend on the BSC driver (or anything else other than for
context). With that in mind I have queued them up in the
sh73a0-multiplatform-for-v3.21 which is based on the dt-for-v3.21 branch
(for context) as part of and pushed this as part of
renesas-devel-20150123-v3.19-rc5.
Please take a moment to see if what I have done makes sense to you.
For reference this covers the following patches which comprised this series:
Magnus Damm (4):
ARM: shmobile: sh73a0: Introduce generic setup callback
ARM: shmobile: sh73a0: Add Multiplatform support
ARM: shmobile: kzm9g dts: Sync with kzm9g-reference dts
ARM: shmobile: kzm9g: Build DTS for Multiplatform
next prev parent reply other threads:[~2015-01-23 4:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 13:08 [PATCH 0/4] ARM: shmobile: sh73a0/kzm9g: Introduce multiplatform support Geert Uytterhoeven
2015-01-09 13:08 ` [PATCH 1/4] ARM: shmobile: sh73a0: Introduce generic setup callback Geert Uytterhoeven
2015-01-09 13:08 ` [PATCH 2/4] ARM: shmobile: sh73a0: Add Multiplatform support Geert Uytterhoeven
2015-01-09 13:08 ` [PATCH 3/4] ARM: shmobile: kzm9g dts: Sync with kzm9g-reference dts Geert Uytterhoeven
2015-01-09 13:08 ` [PATCH 4/4] ARM: shmobile: kzm9g: Build DTS for Multiplatform Geert Uytterhoeven
2015-01-13 2:08 ` [PATCH 0/4] ARM: shmobile: sh73a0/kzm9g: Introduce multiplatform support Simon Horman
2015-01-22 2:48 ` Simon Horman
2015-01-22 2:50 ` Simon Horman
2015-01-23 4:22 ` Simon Horman [this message]
2015-01-23 9:56 ` Geert Uytterhoeven
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=20150123042255.GC17548@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).