From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Heiko Stuebner" <heiko@sntech.de>
Cc: linux-mediatek@lists.infradead.org,
Douglas Anderson <dianders@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
linux-pwm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Benson Leung <bleung@chromium.org>,
linux-arm-msm@vger.kernel.org, chrome-platform@lists.linux.dev,
devicetree@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-rockchip@lists.infradead.org,
Andy Gross <agross@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Guenter Roeck <groeck@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/4] mfd/pwm: dt-bindings: google, cros-ec: include generic pwm schema
Date: Wed, 23 Feb 2022 08:09:39 +0100 [thread overview]
Message-ID: <18bdf4ae-c445-ad10-b344-324436cbe445@canonical.com> (raw)
In-Reply-To: <20220223062233.4m2xejozz4d47gmo@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
next prev parent reply other threads:[~2022-02-23 7:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 8:19 [PATCH 0/4] mfd/pwm: dt-bindings: google,cros-ec: include generic pwm schema Krzysztof Kozlowski
2022-02-14 8:19 ` [PATCH 1/4] dt-bindings: pwm: " Krzysztof Kozlowski
2022-02-22 21:13 ` Rob Herring
2022-02-23 9:16 ` Lee Jones
2022-02-23 22:57 ` Heiko Stuebner
2022-02-24 10:02 ` Lee Jones
2022-02-24 10:06 ` Heiko Stuebner
2022-02-24 10:14 ` Krzysztof Kozlowski
2022-02-24 11:44 ` Lee Jones
2022-02-24 12:41 ` Thierry Reding
2022-02-24 12:51 ` Lee Jones
2022-02-14 8:19 ` [PATCH 2/4] arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema Krzysztof Kozlowski
2022-02-14 15:21 ` AngeloGioacchino Del Regno
2022-03-02 19:06 ` Krzysztof Kozlowski
2022-04-19 10:12 ` (subset) " Krzysztof Kozlowski
2022-02-14 8:19 ` [PATCH 3/4] arm64: dts: qcom: " Krzysztof Kozlowski
2022-02-14 16:21 ` Doug Anderson
2022-02-24 20:54 ` (subset) " Bjorn Andersson
2022-02-14 8:19 ` [PATCH 4/4] arm64: dts: rk3399: " Krzysztof Kozlowski
2022-02-14 16:22 ` Doug Anderson
2022-02-22 23:27 ` (subset) [PATCH 0/4] mfd/pwm: dt-bindings: google, cros-ec: include generic pwm schema Heiko Stuebner
2022-02-23 6:22 ` Uwe Kleine-König
2022-02-23 7:09 ` Krzysztof Kozlowski [this message]
2022-04-04 17:02 ` [PATCH 0/4] mfd/pwm: dt-bindings: google,cros-ec: " patchwork-bot+chrome-platform
2022-04-04 17:14 ` patchwork-bot+chrome-platform
2022-04-04 17:16 ` Heiko Stübner
2022-04-04 17:20 ` Benson Leung
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18bdf4ae-c445-ad10-b344-324436cbe445@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=heiko@sntech.de \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox