From: Rob Herring <robh@kernel.org>
To: cl@rock-chips.com
Cc: linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
zhangqing@rock-chips.com, jbx6244@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, heiko@sntech.de,
lee.jones@linaro.org
Subject: Re: [PATCH v1 2/3] dt-binding: mfd: syscon: add rk3568 QoS register compatible
Date: Wed, 14 Jul 2021 13:32:05 -0600 [thread overview]
Message-ID: <20210714193205.GA3129835@robh.at.kernel.org> (raw)
In-Reply-To: <20210624114719.1685-3-cl@rock-chips.com>
On Thu, 24 Jun 2021 19:47:18 +0800, cl@rock-chips.com wrote:
> From: Liang Chen <cl@rock-chips.com>
>
> Document rk3568 compatible for QoS registers.
>
> Signed-off-by: Liang Chen <cl@rock-chips.com>
> ---
> Documentation/devicetree/bindings/mfd/syscon.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-14 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 11:47 [PATCH v1 0/3] arm64: dts: rockchip: add pmu and qos nodes for rk3568 cl
2021-06-24 11:47 ` [PATCH v1 1/3] dt-bindings: arm: rockchip: add rk3568 compatible string to pmu.yaml cl
2021-07-14 19:27 ` Rob Herring
2021-06-24 11:47 ` [PATCH v1 2/3] dt-binding: mfd: syscon: add rk3568 QoS register compatible cl
2021-07-14 19:32 ` Rob Herring [this message]
2021-07-14 19:57 ` Heiko Stübner
2021-07-15 11:15 ` Lee Jones
2021-06-24 11:47 ` [PATCH v1 3/3] arm64: dts: rockchip: add pmu and qos nodes for rk3568 cl
2021-06-24 12:51 ` Johan Jonker
2021-06-24 13:10 ` [RESEND PATCH " cl
2021-07-15 22:42 ` (subset) [PATCH v1 0/3] " Heiko Stuebner
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=20210714193205.GA3129835@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.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).