From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Johan Jonker <jbx6244@gmail.com>,
heiko@sntech.de, zhangqing@rock-chips.com
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: clock: convert rockchip, rk3368-cru.txt to YAML
Date: Tue, 29 Mar 2022 19:25:57 +0200 [thread overview]
Message-ID: <403f831c-6a19-8ede-9dfe-6b033d1292b4@linaro.org> (raw)
In-Reply-To: <20220329172120.30328-1-jbx6244@gmail.com>
On 29/03/2022 19:21, Johan Jonker wrote:
> Current dts files with RK3368 'cru' nodes are manually verified.
> In order to automate this process rockchip,rk3368-cru.txt has to be
> converted to YAML.
>
> Changed:
> Add properties to fix notifications by clocks.yaml for example:
I see you are on a conversion spree. :) Thanks for the work. Please
shorten the subject as I proposed for 3328. Also this "Changed" and
"notifications" are confusing. There are no notifications here.
This could be something like:
Changes against original bindings:
- Add clocks and clock-names because the device has at least one input
clocks.
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2022-03-29 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 17:21 [PATCH v1 1/2] dt-bindings: clock: convert rockchip, rk3368-cru.txt to YAML Johan Jonker
2022-03-29 17:21 ` [PATCH v1 2/2] arm64: rockchip: add clocks property to cru node rk3368 Johan Jonker
2022-03-29 17:25 ` Krzysztof Kozlowski [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=403f831c-6a19-8ede-9dfe-6b033d1292b4@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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