[PATCH 0/4] ARM: shmobile: sh73a0/kzm9g: Complete multiplatform support
horms at verge.net.au
Wed Jan 14 15:34:12 PST 2015
On Wed, Jan 14, 2015 at 11:03:42AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
> On Wed, Jan 14, 2015 at 5:08 AM, Simon Horman <horms at verge.net.au> wrote:
> > On Tue, Jan 13, 2015 at 11:08:20AM +0100, Geert Uytterhoeven wrote:
> >> On Tue, Jan 13, 2015 at 3:08 AM, Simon Horman <horms at verge.net.au> wrote:
> >> > On Fri, Jan 09, 2015 at 02:24:26PM +0100, Geert Uytterhoeven wrote:
> >> >> This patch series completes the migration from kzm9g-reference (legacy
> >> >> DT based) to kzm9g-multiplatform (ARM multiplatform DT based with
> >> >> common clock framework).
> >> >>
> >> >> - The first two patches fix Ethernet on kzm9g, by adding a Bus State
> >> >> Controller node, as introduced in "[PATCH v3 0/4] drivers: bus:
> >> >> Add Simple Power-Managed Bus", and moving the Ethernet node to it,
> >> >> - The third path enables kzm9g support in shmobile_defconfig,
> >> >> - The fourth patch removes all kzm9g-reference support, now the
> >> >> sh73a0 generic multiplatform case has the same feature set
> >> >> (better, it provides 16 MiB more RAM!).
> >> >>
> >> >> Thanks for applying!
> >> >
> >> > It seems to me that at the first two patches require the patchset
> >> > referenced above in order to work. For that reason I am holding off
> >> Yes it does.
> >> > on applying this series. I am quite happy to negotiate merging
> >> > some or all of this series earlier than later :)
> >> Hence please merge both the dependency and this series.
> >> 1. Both sh73a0/kzm9g-multiplatform and r8a73a4/ape6evm-multiplatform
> >> depend on "[PATCH v3 0/4] drivers: bus: Add Simple Power-Managed Bus",
> > For some reason I assumed this would go through a different subsystem tree.
> > I'm fine with taking it through my tree, if you think that is best.
> There's no maintainer for drivers/bus/, and as kzm9g-multiplatform depends on
> it, your tree looks fine to me.
On closer examination I also see that there is no drivers/bus/ maintainer.
So yes, I agree we should be fine.
> > I am a bit worried about handling conflicts that may arise, especially from
> > the first two patches in that series which re-arrange things
> > alphabetically. But I see that the files in question are not updated very
> > often, so I suppose we should be safe enough.
> > For now I have tentatively queued up both this patchset and the
> > dependency listed immediately above. Please take a look
> > at the sh73a0-multiplatform-for-v3.20 and drivers-for-v3.20 branches
> > and the renesas-next-20150114-v3.19-rc1 tag to see if I missed something.
> Thanks, looks fine!
Great, thanks for checking.
My plan is to send pull-requests for those branches once they
have sat in next for a little bit. By my calculations that should be early
More information about the linux-arm-kernel