| Message ID | 20230913-bloomers-scorebook-fb45e0a2aa19@spud (mailing list archive) |
|---|---|
| Headers | show |
| Series | Missed starfive pmdomain changes for v6.6, now for v6.7 | expand |
On Wed, 13 Sept 2023 at 15:56, Conor Dooley <conor@kernel.org> wrote: > > From: Conor Dooley <conor.dooley@microchip.com> > > Hey Uffe, > > Here's those missed changes in patch form. I figured it might be a bit > easier this way given the name of the subsystem is in flux, doubly so if > you'd like to put the header change of Rob's on fixes. Not sure we really need to queue up patch 1 for fixes - or is it fixing a real problem for us? > > I had this out for LKP last night, seemed to get a clean bill of health, > before I rebased it on top of the new name this afternoon, and ofc it was > in linux-next on top of v6.5 for quite a while... > > Thanks, > Conor. > > CC: arnd@arndb.de > CC: changhuang.liang@starfivetech.com > CC: jiajie.ho@starfivetech.com > CC: linux-pm@vger.kernel.org > CC: linux-riscv@lists.infradead.org > CC: robh@kernel.org > CC: ulf.hansson@linaro.org > CC: walker.chen@starfivetech.com > > Changhuang Liang (4): > dt-bindings: power: Add power-domain header for JH7110 > pmdomain: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE > pmdomain: starfive: Extract JH7110 pmu private operations > pmdomain: starfive: Add JH7110 AON PMU support > > Rob Herring (1): > pmdomain: starfive: Explicitly include correct DT includes > > MAINTAINERS | 1 + > drivers/pmdomain/starfive/jh71xx-pmu.c | 139 ++++++++++++++---- > drivers/soc/starfive/Kconfig | 4 +- > .../dt-bindings/power/starfive,jh7110-pmu.h | 5 +- > 4 files changed, 117 insertions(+), 32 deletions(-) > The series applied for next, thanks! Kind regards Uffe
Yo, I tried to reply a few hours ago from k9, but it appears to not have landed on lore, so here goes attempt #2. Apologies if you got a mail twice. On Thu, Sep 14, 2023 at 12:30:20AM +0200, Ulf Hansson wrote: > On Wed, 13 Sept 2023 at 15:56, Conor Dooley <conor@kernel.org> wrote: > > > > From: Conor Dooley <conor.dooley@microchip.com> > > > > Hey Uffe, > > > > Here's those missed changes in patch form. I figured it might be a bit > > easier this way given the name of the subsystem is in flux, doubly so if > > you'd like to put the header change of Rob's on fixes. > > Not sure we really need to queue up patch 1 for fixes - or is it > fixing a real problem for us? It was just in case you felt that taking that header cleanup as a fix was worthwhile. I think I saw some people doing that last cycle & I think Rob was trying to clean that up for v6.6 which I obviously haven't helped him with. > The series applied for next, thanks! Great, thanks.
On Wed, Sep 13, 2023 at 5:31 PM Ulf Hansson <ulf.hansson@linaro.org> wrote: > > On Wed, 13 Sept 2023 at 15:56, Conor Dooley <conor@kernel.org> wrote: > > > > From: Conor Dooley <conor.dooley@microchip.com> > > > > Hey Uffe, > > > > Here's those missed changes in patch form. I figured it might be a bit > > easier this way given the name of the subsystem is in flux, doubly so if > > you'd like to put the header change of Rob's on fixes. > > Not sure we really need to queue up patch 1 for fixes - or is it > fixing a real problem for us? It's a dependency to remove some implicit includes, but I still have more fixes for 6.6 so either is fine. Rob
On Thu, 14 Sept 2023 at 15:57, Rob Herring <robh@kernel.org> wrote: > > On Wed, Sep 13, 2023 at 5:31 PM Ulf Hansson <ulf.hansson@linaro.org> wrote: > > > > On Wed, 13 Sept 2023 at 15:56, Conor Dooley <conor@kernel.org> wrote: > > > > > > From: Conor Dooley <conor.dooley@microchip.com> > > > > > > Hey Uffe, > > > > > > Here's those missed changes in patch form. I figured it might be a bit > > > easier this way given the name of the subsystem is in flux, doubly so if > > > you'd like to put the header change of Rob's on fixes. > > > > Not sure we really need to queue up patch 1 for fixes - or is it > > fixing a real problem for us? > > It's a dependency to remove some implicit includes, but I still have > more fixes for 6.6 so either is fine. Okay, I keep it for v6.7 then. Just let me know if things change then I can move it to v6.6-rcs Kind regards Uffe
From: Conor Dooley <conor.dooley@microchip.com> Hey Uffe, Here's those missed changes in patch form. I figured it might be a bit easier this way given the name of the subsystem is in flux, doubly so if you'd like to put the header change of Rob's on fixes. I had this out for LKP last night, seemed to get a clean bill of health, before I rebased it on top of the new name this afternoon, and ofc it was in linux-next on top of v6.5 for quite a while... Thanks, Conor. CC: arnd@arndb.de CC: changhuang.liang@starfivetech.com CC: jiajie.ho@starfivetech.com CC: linux-pm@vger.kernel.org CC: linux-riscv@lists.infradead.org CC: robh@kernel.org CC: ulf.hansson@linaro.org CC: walker.chen@starfivetech.com Changhuang Liang (4): dt-bindings: power: Add power-domain header for JH7110 pmdomain: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE pmdomain: starfive: Extract JH7110 pmu private operations pmdomain: starfive: Add JH7110 AON PMU support Rob Herring (1): pmdomain: starfive: Explicitly include correct DT includes MAINTAINERS | 1 + drivers/pmdomain/starfive/jh71xx-pmu.c | 139 ++++++++++++++---- drivers/soc/starfive/Kconfig | 4 +- .../dt-bindings/power/starfive,jh7110-pmu.h | 5 +- 4 files changed, 117 insertions(+), 32 deletions(-)