From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: David Yang <mmyangfl@gmail.com>, linux-clk@vger.kernel.org
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] clk: Add basic register clock controller
Date: Mon, 17 Apr 2023 08:27:47 +0200 [thread overview]
Message-ID: <81ed4e15-19ea-34d9-3e05-d1195b2cdd57@linaro.org> (raw)
In-Reply-To: <20230416194624.1258860-1-mmyangfl@gmail.com>
On 16/04/2023 21:46, David Yang wrote:
> These clocks were provided in `include/linux/clk-provider.h`, but lacks DT
> bindings. Add DT bindings for them.
>
> v2: split clock controller and its clocks
I gave you several comments on v1 and this vague changelog entry
suggests you ignored all of it.
Implement feedback and respond to each one that you ack it or disagree
with it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-17 6:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 19:46 [PATCH v3 0/4] clk: Add basic register clock controller David Yang
2023-04-16 19:46 ` [PATCH v3 1/4] dt-bindings: clock: Add simple-clock-controller David Yang
2023-04-17 6:28 ` Krzysztof Kozlowski
2023-04-17 6:30 ` Krzysztof Kozlowski
2023-04-16 19:46 ` [PATCH v3 2/4] clk: Add simple clock controller David Yang
2023-04-18 19:12 ` kernel test robot
2023-04-16 19:46 ` [PATCH v3 3/4] dt-bindings: clock: Add gate-clock David Yang
2023-04-18 0:12 ` Stephen Boyd
2023-04-16 19:46 ` [PATCH v3 4/4] clk: gate: Add DT binding David Yang
2023-04-17 6:27 ` Krzysztof Kozlowski [this message]
2023-04-17 18:16 ` [PATCH v3 0/4] clk: Add basic register clock controller Yangfl
2023-04-18 22:29 ` Rob Herring
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=81ed4e15-19ea-34d9-3e05-d1195b2cdd57@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
/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).