From: Rob Herring <robh@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
cl@rock-chips.com, thierry.reding@gmail.com, heiko@sntech.de,
jagan@amarulasolutions.com, wens@csie.org, uwe@kleine-koenig.org,
mail@david-bauer.net, jbx6244@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
jensenhuang@friendlyarm.com, michael@amarulasolutions.com,
cnsztl@gmail.com, devicetree@vger.kernel.org,
ulf.hansson@linaro.org, linux-mmc@vger.kernel.org,
gregkh@linuxfoundation.org, linux-serial@vger.kernel.org,
linux-i2c@vger.kernel.org, jay.xu@rock-chips.com,
shawn.lin@rock-chips.com, david.wu@rock-chips.com,
zhangqing@rock-chips.com, huangtao@rock-chips.com,
wim@linux-watchdog.org, linux@roeck-us.net, jamie@jamieiles.com,
linux-watchdog@vger.kernel.org, maz@kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [RESEND PATCH v5 1/4] dt-bindings: pwm: rockchip: add description for rk3568
Date: Tue, 13 Jul 2021 16:57:09 -0600 [thread overview]
Message-ID: <20210713225709.GA987961@robh.at.kernel.org> (raw)
In-Reply-To: <YOK1+pMy+N64eR75@dell>
On Mon, Jul 05, 2021 at 08:34:18AM +0100, Lee Jones wrote:
> On Mon, 05 Jul 2021, Uwe Kleine-König wrote:
>
> > On Wed, Jun 23, 2021 at 10:13:03AM +0800, cl@rock-chips.com wrote:
> > > From: Liang Chen <cl@rock-chips.com>
> > >
> > > add "rockchip,rk3568-pwm", "rockchip,rk3328-pwm" for pwm nodes on
> > > a rk3568 platform to pwm-rockchip.yaml.
> >
> > Looks good to me
> >
> > Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> >
> > Who is supposed to apply this patch? Does this need blessing by Rob?
>
> There is no standard. Rob will usually have some kind of arrangement
> with the associated maintainer(s). If this is a big functional
> change, I would suggest letting Rob and his army of bots give it the
> once over before it is applied in any case.
The documented standard[1] is subsystem maintainers take bindings. Are
there exceptions? Yes. Usually that's standalone patches (which netdev
maintainers just ignore for example).
One line compatible string changes don't need to wait for me.
Rob
[1] https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/tree/Documentation/devicetree/bindings/submitting-patches.rst#n67
next prev parent reply other threads:[~2021-07-13 22:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 2:05 [PATCH v5 0/4] arm64: dts: rockchip: add basic dtsi/dts files for RK3568 SoC cl
2021-06-22 2:05 ` [PATCH v5 1/4] dt-bindings: pwm: rockchip: add description for rk3568 cl
2021-06-22 10:53 ` Heiko Stübner
2021-07-26 9:05 ` Heiko Stübner
2021-06-22 2:05 ` [PATCH v5 2/4] arm64: dts: rockchip: add generic pinconfig settings used by most Rockchip socs cl
2021-06-22 2:05 ` [PATCH v5 3/4] arm64: dts: rockchip: add core dtsi for RK3568 SoC cl
2021-06-22 10:37 ` Johan Jonker
2021-06-22 10:52 ` Heiko Stübner
2021-06-22 2:05 ` [PATCH v5 4/4] arm64: dts: rockchip: add basic dts for RK3568 EVB cl
2021-06-22 10:26 ` (subset) [PATCH v5 0/4] arm64: dts: rockchip: add basic dtsi/dts files for RK3568 SoC Heiko Stuebner
2021-06-23 2:13 ` [RESEND PATCH v5 1/4] dt-bindings: pwm: rockchip: add description for rk3568 cl
2021-07-05 6:49 ` Uwe Kleine-König
2021-07-05 7:34 ` Lee Jones
2021-07-05 7:44 ` Uwe Kleine-König
2021-07-11 17:44 ` Heiko Stübner
2021-07-13 22:57 ` Rob Herring [this message]
2021-07-13 22:58 ` Rob Herring
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=20210713225709.GA987961@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cl@rock-chips.com \
--cc=cnsztl@gmail.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jagan@amarulasolutions.com \
--cc=jamie@jamieiles.com \
--cc=jay.xu@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=jensenhuang@friendlyarm.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mail@david-bauer.net \
--cc=maz@kernel.org \
--cc=michael@amarulasolutions.com \
--cc=shawn.lin@rock-chips.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=ulf.hansson@linaro.org \
--cc=uwe@kleine-koenig.org \
--cc=wens@csie.org \
--cc=wim@linux-watchdog.org \
--cc=zhangqing@rock-chips.com \
/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).