From: Heiko Stuebner <heiko@sntech.de>
To: zhangqing@rock-chips.com, Johan Jonker <jbx6244@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
robh+dt@kernel.org, linux-rockchip@lists.infradead.org,
sboyd@kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: clock: convert rockchip, rk3308-cru.txt to YAML
Date: Tue, 17 May 2022 21:11:14 +0200 [thread overview]
Message-ID: <165281458742.3119039.4240634682274966111.b4-ty@sntech.de> (raw)
In-Reply-To: <20220329184339.1134-1-jbx6244@gmail.com>
On Tue, 29 Mar 2022 20:43:38 +0200, Johan Jonker wrote:
> Convert rockchip,rk3308-cru.txt to YAML.
>
> Changes against original bindings:
> - Add clocks and clock-names because the device has to have
> at least one input clock.
Applied, thanks!
[1/2] dt-bindings: clock: convert rockchip,rk3308-cru.txt to YAML
commit: d87642d72e2921517a01139f33652dbb819a8115
[2/2] arm64: rockchip: add clocks property to cru node rk3308
commit: d7283a95de1a0e9c1c2a99e1d643fa391010fb0a
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-17 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 18:43 [PATCH v1 1/2] dt-bindings: clock: convert rockchip, rk3308-cru.txt to YAML Johan Jonker
2022-03-29 18:43 ` [PATCH v1 2/2] arm64: rockchip: add clocks property to cru node rk3308 Johan Jonker
2022-03-29 19:05 ` [PATCH v1 1/2] dt-bindings: clock: convert rockchip, rk3308-cru.txt to YAML Krzysztof Kozlowski
2022-05-17 19:11 ` Heiko Stuebner [this message]
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=165281458742.3119039.4240634682274966111.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jbx6244@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).