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 v3 1/2] dt-bindings: clock: convert rockchip, rk3188-cru.txt to YAML
Date: Tue, 29 Mar 2022 13:43:20 +0200 [thread overview]
Message-ID: <5ea0386f-5322-4efd-c0d0-0ba0ff526bae@linaro.org> (raw)
In-Reply-To: <20220329111323.3569-1-jbx6244@gmail.com>
On 29/03/2022 13:13, Johan Jonker wrote:
> Current dts files with RK3188/RK3066 'cru' nodes are manually verified.
> In order to automate this process rockchip,rk3188-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>
> ---
>
It's the second patchset without my review. What's happening here?
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-29 11:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 11:13 [PATCH v3 1/2] dt-bindings: clock: convert rockchip,rk3188-cru.txt to YAML Johan Jonker
2022-03-29 11:13 ` [PATCH v3 2/2] ARM: dts: rockchip: add clocks property to cru node rk3066a/rk3188 Johan Jonker
2022-03-29 11:43 ` Krzysztof Kozlowski [this message]
2022-03-31 22:51 ` [PATCH v3 1/2] dt-bindings: clock: convert rockchip,rk3188-cru.txt to YAML Stephen Boyd
2022-04-01 7:55 ` Heiko Stübner
2022-04-01 18:24 ` Stephen Boyd
2022-04-02 11:41 ` Krzysztof Kozlowski
2022-04-02 11:45 ` Johan Jonker
2022-04-02 12:16 ` Krzysztof Kozlowski
2022-04-02 12:20 ` Johan Jonker
2022-04-02 16:01 ` Krzysztof Kozlowski
2022-04-06 16:18 ` Heiko Stuebner
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=5ea0386f-5322-4efd-c0d0-0ba0ff526bae@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;
as well as URLs for NNTP newsgroup(s).