From: "Heiko Stübner" <heiko@sntech.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
patchwork-bot+chrome-platform@kernel.org
Cc: lee.jones@linaro.org, robh+dt@kernel.org, bleung@chromium.org,
groeck@chromium.org, thierry.reding@gmail.com,
u.kleine-koenig@pengutronix.de, matthias.bgg@gmail.com,
agross@kernel.org, bjorn.andersson@linaro.org,
dianders@chromium.org, devicetree@vger.kernel.org,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 0/4] mfd/pwm: dt-bindings: google,cros-ec: include generic pwm schema
Date: Mon, 04 Apr 2022 19:16:03 +0200 [thread overview]
Message-ID: <2259298.ElGaqSPkdT@diego> (raw)
In-Reply-To: <164909246180.14329.3397709419938843373.git-patchwork-notify@kernel.org>
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!
>
next prev parent reply other threads:[~2022-04-04 21:17 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
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 [this message]
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=2259298.ElGaqSPkdT@diego \
--to=heiko@sntech.de \
--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=krzysztof.kozlowski@canonical.com \
--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=patchwork-bot+chrome-platform@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).