Message ID | cover.1419809955.git.horms+renesas@verge.net.au |
---|---|
State | New |
Headers | show |
On Mon, Dec 29, 2014 at 10:46:58AM +0900, Simon Horman wrote: > Hi Olof, Hi Kevin, Hi Arnd, > > Please consider these Renesas ARM based SoC sh73a0 CCF updates for v3.20. > > > The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672: > > Linux 3.19-rc1 (2014-12-20 17:08:50 -0800) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-sh73a0-ccf-for-v3.20 > > for you to fetch changes up to 09bd745b555c262d1e2c851777317f3adf3cf3d4: > > ARM: shmobile: sh73a0: disable legacy clock initialization (2014-12-21 17:09:25 +0900) This could really have been sliced slightly differently with the drivers/clk change going in a drivers branch, but that might be a bit too messy given that this is better done as a mostly-atomic switch over. I've merged this into next/drivers as a whole now. Please be careful with conflicts against this branch with other new additions this cycle. -Olof
On Mon, Jan 12, 2015 at 02:34:15PM -0800, Olof Johansson wrote: > On Mon, Dec 29, 2014 at 10:46:58AM +0900, Simon Horman wrote: > > Hi Olof, Hi Kevin, Hi Arnd, > > > > Please consider these Renesas ARM based SoC sh73a0 CCF updates for v3.20. > > > > > > The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672: > > > > Linux 3.19-rc1 (2014-12-20 17:08:50 -0800) > > > > are available in the git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-sh73a0-ccf-for-v3.20 > > > > for you to fetch changes up to 09bd745b555c262d1e2c851777317f3adf3cf3d4: > > > > ARM: shmobile: sh73a0: disable legacy clock initialization (2014-12-21 17:09:25 +0900) > > This could really have been sliced slightly differently with the drivers/clk > change going in a drivers branch, but that might be a bit too messy given that > this is better done as a mostly-atomic switch over. > > I've merged this into next/drivers as a whole now. Please be careful with > conflicts against this branch with other new additions this cycle. Thanks. The motivation for this branch arrangement was indeed the atomic switch over.
On Tue, Jan 13, 2015 at 1:38 AM, Simon Horman <horms@verge.net.au> wrote: > On Mon, Jan 12, 2015 at 02:34:15PM -0800, Olof Johansson wrote: >> On Mon, Dec 29, 2014 at 10:46:58AM +0900, Simon Horman wrote: >> > Hi Olof, Hi Kevin, Hi Arnd, >> > >> > Please consider these Renesas ARM based SoC sh73a0 CCF updates for v3.20. >> > >> > >> > The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672: >> > >> > Linux 3.19-rc1 (2014-12-20 17:08:50 -0800) >> > >> > are available in the git repository at: >> > >> > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-sh73a0-ccf-for-v3.20 >> > >> > for you to fetch changes up to 09bd745b555c262d1e2c851777317f3adf3cf3d4: >> > >> > ARM: shmobile: sh73a0: disable legacy clock initialization (2014-12-21 17:09:25 +0900) >> >> This could really have been sliced slightly differently with the drivers/clk >> change going in a drivers branch, but that might be a bit too messy given that >> this is better done as a mostly-atomic switch over. >> >> I've merged this into next/drivers as a whole now. Please be careful with >> conflicts against this branch with other new additions this cycle. > > 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. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
On Tue, Jan 13, 2015 at 09:12:53AM +0100, Geert Uytterhoeven wrote: > On Tue, Jan 13, 2015 at 1:38 AM, Simon Horman <horms@verge.net.au> wrote: > > On Mon, Jan 12, 2015 at 02:34:15PM -0800, Olof Johansson wrote: > >> On Mon, Dec 29, 2014 at 10:46:58AM +0900, Simon Horman wrote: > >> > Hi Olof, Hi Kevin, Hi Arnd, > >> > > >> > Please consider these Renesas ARM based SoC sh73a0 CCF updates for v3.20. > >> > > >> > > >> > The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672: > >> > > >> > Linux 3.19-rc1 (2014-12-20 17:08:50 -0800) > >> > > >> > are available in the git repository at: > >> > > >> > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-sh73a0-ccf-for-v3.20 > >> > > >> > for you to fetch changes up to 09bd745b555c262d1e2c851777317f3adf3cf3d4: > >> > > >> > ARM: shmobile: sh73a0: disable legacy clock initialization (2014-12-21 17:09:25 +0900) > >> > >> This could really have been sliced slightly differently with the drivers/clk > >> change going in a drivers branch, but that might be a bit too messy given that > >> this is better done as a mostly-atomic switch over. > >> > >> I've merged this into next/drivers as a whole now. Please be careful with > >> conflicts against this branch with other new additions this cycle. > > > > 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? 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. To be clear, I'm not suggesting changing this pull-request which has already been accepted. > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds >
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 ;-) Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
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.