Documentation/devicetree/bindings/mfd/google,cros-ec.yaml | 4 ++++ .../devicetree/bindings/pwm/google,cros-ec-pwm.yaml | 5 ++++- arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi | 2 +- arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi | 2 +- arch/arm64/boot/dts/qcom/sc7280-herobrine-herobrine-r0.dts | 2 +- arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi | 2 +- arch/arm64/boot/dts/qcom/sc7280-idp-ec-h1.dtsi | 2 +- arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 2 +- arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi | 2 +- 9 files changed, 15 insertions(+), 8 deletions(-)
Hi, DTS patches are independent. Not tested, but I really hope no downstream kernel depends on pwm node naming... If it does, please change it to compatible. :) Best regards, Krzysztof Krzysztof Kozlowski (4): dt-bindings: pwm: google,cros-ec: include generic pwm schema arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema arm64: dts: qcom: align Google CROS EC PWM node name with dtschema arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema Documentation/devicetree/bindings/mfd/google,cros-ec.yaml | 4 ++++ .../devicetree/bindings/pwm/google,cros-ec-pwm.yaml | 5 ++++- arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi.dtsi | 2 +- arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi | 2 +- arch/arm64/boot/dts/qcom/sc7280-herobrine-herobrine-r0.dts | 2 +- arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi | 2 +- arch/arm64/boot/dts/qcom/sc7280-idp-ec-h1.dtsi | 2 +- arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 2 +- arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi | 2 +- 9 files changed, 15 insertions(+), 8 deletions(-) -- 2.32.0
Hello: This series was applied to chrome-platform/linux.git (for-kernelci) by Heiko Stuebner <heiko@sntech.de>: On Mon, 14 Feb 2022 09:19:12 +0100 you wrote: > Hi, > > DTS patches are independent. Not tested, but I really hope no downstream kernel > depends on pwm node naming... If it does, please change it to compatible. :) > > Best regards, > Krzysztof > > [...] Here is the summary with links: - [1/4] dt-bindings: pwm: google,cros-ec: include generic pwm schema https://git.kernel.org/chrome-platform/c/6b94ee669e8a - [2/4] arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema (no matching commit) - [3/4] arm64: dts: qcom: align Google CROS EC PWM node name with dtschema https://git.kernel.org/chrome-platform/c/1e49defb8636 - [4/4] arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema https://git.kernel.org/chrome-platform/c/a0024f55eb5b You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Hello: This series was applied to chrome-platform/linux.git (for-next) by Heiko Stuebner <heiko@sntech.de>: On Mon, 14 Feb 2022 09:19:12 +0100 you wrote: > Hi, > > DTS patches are independent. Not tested, but I really hope no downstream kernel > depends on pwm node naming... If it does, please change it to compatible. :) > > Best regards, > Krzysztof > > [...] Here is the summary with links: - [1/4] dt-bindings: pwm: google,cros-ec: include generic pwm schema https://git.kernel.org/chrome-platform/c/6b94ee669e8a - [2/4] arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema (no matching commit) - [3/4] arm64: dts: qcom: align Google CROS EC PWM node name with dtschema https://git.kernel.org/chrome-platform/c/1e49defb8636 - [4/4] arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema https://git.kernel.org/chrome-platform/c/a0024f55eb5b You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Am Montag, 4. April 2022, 19:14:21 CEST schrieb patchwork-bot+chrome-platform@kernel.org: > Hello: > > This series was applied to chrome-platform/linux.git (for-next) > by Heiko Stuebner <heiko@sntech.de>: does someone know what goes on here? I did apply only patch4 back in feburary and I definitly don't have any access to a chrome-platform tree ;-) Heiko > On Mon, 14 Feb 2022 09:19:12 +0100 you wrote: > > Hi, > > > > DTS patches are independent. Not tested, but I really hope no downstream kernel > > depends on pwm node naming... If it does, please change it to compatible. :) > > > > Best regards, > > Krzysztof > > > > [...] > > Here is the summary with links: > - [1/4] dt-bindings: pwm: google,cros-ec: include generic pwm schema > https://git.kernel.org/chrome-platform/c/6b94ee669e8a > - [2/4] arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema > (no matching commit) > - [3/4] arm64: dts: qcom: align Google CROS EC PWM node name with dtschema > https://git.kernel.org/chrome-platform/c/1e49defb8636 > - [4/4] arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema > https://git.kernel.org/chrome-platform/c/a0024f55eb5b > > You are awesome, thank you! >
Hi Heiko, On Mon, Apr 04, 2022 at 07:16:03PM +0200, Heiko Stübner wrote: > Am Montag, 4. April 2022, 19:14:21 CEST schrieb patchwork-bot+chrome-platform@kernel.org: > > Hello: > > > > This series was applied to chrome-platform/linux.git (for-next) > > by Heiko Stuebner <heiko@sntech.de>: > > does someone know what goes on here? > > I did apply only patch4 back in feburary and I definitly don't have any > access to a chrome-platform tree ;-) > Sorry for the extra noise. It looks like patchwork-bot did this once I updated chrome-platform's for-next branch to the newly created v5.18-rc1, which contains this series now. I'll look into quieting this in the future. Benson > > Heiko > > > On Mon, 14 Feb 2022 09:19:12 +0100 you wrote: > > > Hi, > > > > > > DTS patches are independent. Not tested, but I really hope no downstream kernel > > > depends on pwm node naming... If it does, please change it to compatible. :) > > > > > > Best regards, > > > Krzysztof > > > > > > [...] > > > > Here is the summary with links: > > - [1/4] dt-bindings: pwm: google,cros-ec: include generic pwm schema > > https://git.kernel.org/chrome-platform/c/6b94ee669e8a > > - [2/4] arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema > > (no matching commit) > > - [3/4] arm64: dts: qcom: align Google CROS EC PWM node name with dtschema > > https://git.kernel.org/chrome-platform/c/1e49defb8636 > > - [4/4] arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema > > https://git.kernel.org/chrome-platform/c/a0024f55eb5b > > > > You are awesome, thank you! > > > > > > -- Benson Leung Staff Software Engineer Chrome OS Kernel Google Inc. bleung@google.com Chromium OS Project bleung@chromium.org
On Mon, 14 Feb 2022 09:19:12 +0100, Krzysztof Kozlowski wrote: > DTS patches are independent. Not tested, but I really hope no downstream kernel > depends on pwm node naming... If it does, please change it to compatible. :) > > Best regards, > Krzysztof > > Krzysztof Kozlowski (4): > dt-bindings: pwm: google,cros-ec: include generic pwm schema > arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema > arm64: dts: qcom: align Google CROS EC PWM node name with dtschema > arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema > > [...] Applied, thanks! [4/4] arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema commit: 474a84be692d893f45a54b405dcbc137cbf77949 Best regards, -- Heiko Stuebner <heiko@sntech.de>
Hello, On Wed, Feb 23, 2022 at 12:27:08AM +0100, Heiko Stuebner wrote: > On Mon, 14 Feb 2022 09:19:12 +0100, Krzysztof Kozlowski wrote: > > DTS patches are independent. Not tested, but I really hope no downstream kernel > > depends on pwm node naming... If it does, please change it to compatible. :) > > > > Best regards, > > Krzysztof > > > > Krzysztof Kozlowski (4): > > dt-bindings: pwm: google,cros-ec: include generic pwm schema > > arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema > > arm64: dts: qcom: align Google CROS EC PWM node name with dtschema > > arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema > > > > [...] > > Applied, thanks! > > [4/4] arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema > commit: 474a84be692d893f45a54b405dcbc137cbf77949 I expected that all patches in this series go in together via an ARM tree. Or are there expectations that this goes via PWM? Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | https://www.pengutronix.de/ |
On 23/02/2022 07:22, Uwe Kleine-König wrote: > Hello, > > On Wed, Feb 23, 2022 at 12:27:08AM +0100, Heiko Stuebner wrote: >> On Mon, 14 Feb 2022 09:19:12 +0100, Krzysztof Kozlowski wrote: >>> DTS patches are independent. Not tested, but I really hope no downstream kernel >>> depends on pwm node naming... If it does, please change it to compatible. :) >>> >>> Best regards, >>> Krzysztof >>> >>> Krzysztof Kozlowski (4): >>> dt-bindings: pwm: google,cros-ec: include generic pwm schema >>> arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema >>> arm64: dts: qcom: align Google CROS EC PWM node name with dtschema >>> arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema >>> >>> [...] >> >> Applied, thanks! >> >> [4/4] arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema >> commit: 474a84be692d893f45a54b405dcbc137cbf77949 > > I expected that all patches in this series go in together via an ARM > tree. Or are there expectations that this goes via PWM? I would propose to pick individual patches by each maintainer. bindings by PWM tree (Rob acked it) and DTS via each SoC tree. Such approach gives flexibility, although `make dtbs_check` will spot the new errors when run in PWM tree. Next will be fine, though. Best regards, Krzysztof
© 2016 - 2024 Red Hat, Inc.