From: Stephen Boyd <sboyd@kernel.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,
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 v2 1/2] dt-bindings: clock: convert rockchip, rk3288-cru.txt to YAML
Date: Thu, 31 Mar 2022 15:54:04 -0700 [thread overview]
Message-ID: <20220331225406.0C945C340ED@smtp.kernel.org> (raw)
In-Reply-To: <20220329113657.4567-1-jbx6244@gmail.com>
Quoting Johan Jonker (2022-03-29 04:36:56)
> Current dts files with RK3288 'cru' nodes are manually verified.
> In order to automate this process rockchip,rk3288-cru.txt has to be
> converted to YAML.
>
> Changed:
> Add properties to fix notifications by clocks.yaml for example:
> clocks
> clock-names
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
Same comments about clocks applies here. Please send a cover letter
anytime there's more than one patch being sent so that we can easily see
the topic at a top-level of the patch series "Convert Rockchip clk
bindings to yaml and add clocks property". Furthermore, I don't see why
we need to have a different series for each file. Just combine
everything into one series please with a cover letter.
_______________________________________________
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:[~2022-03-31 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 11:36 [PATCH v2 1/2] dt-bindings: clock: convert rockchip, rk3288-cru.txt to YAML Johan Jonker
2022-03-29 11:36 ` [PATCH v2 2/2] ARM: dts: rockchip: add clocks property to cru node rk3288 Johan Jonker
2022-03-29 11:42 ` [PATCH v2 1/2] dt-bindings: clock: convert rockchip, rk3288-cru.txt to YAML Krzysztof Kozlowski
2022-03-31 22:54 ` Stephen Boyd [this message]
2022-05-17 19:11 ` 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=20220331225406.0C945C340ED@smtp.kernel.org \
--to=sboyd@kernel.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=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).