Message ID | 7ho907rfsf.fsf@baylibre.com (mailing list archive) |
---|---|
State | Not Applicable |
Headers | show |
Series | [GIT,PULL] soc: amlogic: updates for v5.4 (round 2) | expand |
Kevin Hilman <khilman@baylibre.com> writes: > The following changes since commit 49ed86f503be80aac158a567c4cfd31cf1cd181e: > > soc: amlogic: meson-gx-socinfo: Add of_node_put() before return (2019-08-20 14:53:33 -0700) > > are available in the Git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git tags/amlogic-drivers-2 > > for you to fetch changes up to eef3c2ba0a42a6aa709828e968b64bd11f4aeb19: > > soc: amlogic: Add support for Everything-Else power domains controller (2019-08-28 14:29:37 -0700) > > ---------------------------------------------------------------- > soc: amlogic: updates for v5.4 (round 2) > - add power domain controller > > ---------------------------------------------------------------- Please ignore. I messed up some dependencies. I'll respin/resend. Kevin
OK, here's the respin (round 2.1) The previous version was missing the bindings for the new driver, which I had mistakenly put in the DT branch instead of here. Without the bindings and associated headers, this branch did not build stanalone (found by kbuild robot.) All that is fixed by this branch. As a result, I also needed to respin the DT64 pull. Since I moved the bindings/header patche here, the respin of the DT64 pull will now have a dependency merge of this branch. Kevin The following changes since commit 49ed86f503be80aac158a567c4cfd31cf1cd181e: soc: amlogic: meson-gx-socinfo: Add of_node_put() before return (2019-08-20 14:53:33 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git tags/amlogic-drivers-2.1 for you to fetch changes up to bd9eccf14008732f8ea4a7efc7839911e56053a1: dt-bindings: power: add Amlogic Everything-Else power domains bindings (2019-08-29 16:05:01 -0700) ---------------------------------------------------------------- soc: amlogic: updates for v5.4 (round 2) - add power domain controller ---------------------------------------------------------------- Neil Armstrong (2): soc: amlogic: Add support for Everything-Else power domains controller dt-bindings: power: add Amlogic Everything-Else power domains bindings Documentation/devicetree/bindings/power/amlogic,meson-ee-pwrc.yaml | 93 +++++++++++++++++++ drivers/soc/amlogic/Kconfig | 11 +++ drivers/soc/amlogic/Makefile | 1 + drivers/soc/amlogic/meson-ee-pwrc.c | 492 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ include/dt-bindings/power/meson-g12a-power.h | 13 +++ include/dt-bindings/power/meson-sm1-power.h | 18 ++++ 6 files changed, 628 insertions(+) create mode 100644 Documentation/devicetree/bindings/power/amlogic,meson-ee-pwrc.yaml create mode 100644 drivers/soc/amlogic/meson-ee-pwrc.c create mode 100644 include/dt-bindings/power/meson-g12a-power.h create mode 100644 include/dt-bindings/power/meson-sm1-power.h
On Fri, Aug 30, 2019 at 1:34 AM Kevin Hilman <khilman@baylibre.com> wrote: > > OK, here's the respin (round 2.1) > > The previous version was missing the bindings for the new driver, which > I had mistakenly put in the DT branch instead of here. Without the > bindings and associated headers, this branch did not build stanalone > (found by kbuild robot.) > > All that is fixed by this branch. > > As a result, I also needed to respin the DT64 pull. Since I moved the > bindings/header patche here, the respin of the DT64 pull will now have a > dependency merge of this branch. I've pulled round 2.1 into arm/drivers, but it seems that the patchwork integration failed to deal with the way this was sent: - https://patchwork.kernel.org/patch/11122205/ shows both the original pull request, and the updated one. It was meant to detect both pull requests as the same thing and mark the old one as superseded, but that did not happen. - Using pwclient to get the pull request only shows the original one - I actually tried pulling that after looking at it with pwclient instead of the email client. Thankfully, you had removed the original tag, so that failed and I took a closer look. I suspect it would have worked the way it did for https://patchwork.kernel.org/patch/11119171/ if you had specified the subject as [GIT PULL, v2] soc: amlogic: updates for v5.4 (round 2) i.e. kept the subject the same but the version inside of the []. Arnd
Arnd Bergmann <arnd@arndb.de> writes: > On Fri, Aug 30, 2019 at 1:34 AM Kevin Hilman <khilman@baylibre.com> wrote: >> >> OK, here's the respin (round 2.1) >> >> The previous version was missing the bindings for the new driver, which >> I had mistakenly put in the DT branch instead of here. Without the >> bindings and associated headers, this branch did not build stanalone >> (found by kbuild robot.) >> >> All that is fixed by this branch. >> >> As a result, I also needed to respin the DT64 pull. Since I moved the >> bindings/header patche here, the respin of the DT64 pull will now have a >> dependency merge of this branch. > > I've pulled round 2.1 into arm/drivers, but it seems that the > patchwork integration > failed to deal with the way this was sent: > > - https://patchwork.kernel.org/patch/11122205/ shows both the original > pull request, and the updated one. It was meant to detect both pull > requests as the same thing and mark the old one as superseded, but that > did not happen. > > - Using pwclient to get the pull request only shows the original one > > - I actually tried pulling that after looking at it with pwclient instead of > the email client. Thankfully, you had removed the original tag, so that > failed and I took a closer look. > > I suspect it would have worked the way it did for > https://patchwork.kernel.org/patch/11119171/ if you had specified > the subject as > > [GIT PULL, v2] soc: amlogic: updates for v5.4 (round 2) > > i.e. kept the subject the same but the version inside of the []. Ah, ok. Good to know. Thanks, Kevin