Re: [GIT PULL] Renesas ARM Based SoC sh73a0 CCF Updates for v3.20

[Simon Horman <horms@verge.net.au>]

On Wed, Jan 14, 2015 at 11:02:04AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Wed, Jan 14, 2015 at 1:29 AM, Simon Horman <horms@verge.net.au> wrote:
> >> > Thanks. The motivation for this branch arrangement was indeed
> >> > the atomic switch over.
> >>
> >> Please correct me if I'm wrong, but IMHO there's no atomicity needed here,
> >> as this won't be used until sh73a0 multi-platform support is in.
> >
> > Ok, it seems that I was slightly mistaken. But we are working towards
> > multi-platform support for v3.20, right?
> 
> Yes we are ;-)
> 
> > Could you take a moment to look at what is currently queued up in
> > the sh73a0-multiplatform-for-v3.20 branch, which is based on this
> > pull-request and see if you think any re-arrangement of that branch
> > is in order.
> 
> You already have drivers-for-v3.20 as a separate branch this depends on.
> The remaining commits are mostly DTS, except for (1)
> 
>     ARM: shmobile: sh73a0: Introduce generic setup callback
>     ARM: shmobile: sh73a0: Add Multiplatform support
> 
> and (1)
> 
>     ARM: shmobile: kzm9g-reference: Remove board C code and DT file
> 
> (1) could be done in an SoC support code branch, as (codewise) it's independent
> from the rest.
> (2) could be done in a board removal branch, but it's only a single commit.
> 
> >From a functionality point of view, (1) (and all the rest in the branch) is a
> dependency of (2), though.
> 
> So if no one complains, I'd leave it as-is. Splitting it up is not
> gonna makes things
> simpler when I submit my next series ;-)

Thanks, for looking into this.
I am inclined to leave things as is as you suggest.