From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alex Elder <elder@riscstar.com>,
sboyd@kernel.org, bmasney+clk@redhat.com,
jbrunet+clk@baylibre.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org
Cc: abelvesa@kernel.org, kees@kernel.org, gustavoars@kernel.org,
mohd.anwar@oss.qualcomm.com, lorenzo.bianconi@oss.qualcomm.com,
danielt@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Thompson <daniel@riscstar.com>
Subject: Re: [PATCH v3 1/4] dt-bindings: clock: introduce toshiba,tc9564-clock.yaml
Date: Wed, 14 Oct 2026 12:18:56 +0200 [thread overview]
Message-ID: <f7ef8af7-e8b4-4ee5-88e2-f3271e10ea9c@kernel.org> (raw)
In-Reply-To: <20261012152408.3729237-2-elder@riscstar.com>
On 12/10/2026 17:24, Alex Elder wrote:
> + syscon@0 {
> + compatible = "syscon", "simple-mfd";
> + reg = <0x0 0x2000>;
None of above are relevant to this example.
> +
> + clock-controller {
> + compatible = "toshiba,tc9564-clock";
> + clocks = <&tc9564_xo_board>;
> + #clock-cells = <1>;
So this is the same as v1. I do not see how you addressed "should be
folded into the parent node.".
I am repeating the same for weeks now, so can we stop with sending new
patches which are exactly the same from the point of view of that comment?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-14 10:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 15:24 [PATCH v3 0/4] clk: introduce TC9564 clock support Alex Elder
2026-10-12 15:24 ` [PATCH v3 1/4] dt-bindings: clock: introduce toshiba,tc9564-clock.yaml Alex Elder
2026-10-12 20:58 ` Conor Dooley
2026-10-14 10:18 ` Krzysztof Kozlowski [this message]
2026-10-12 15:24 ` [PATCH v3 2/4] clk: toshiba: introduce a TC9564 SoC clock driver Alex Elder
2026-10-12 19:02 ` Alex Elder
2026-10-12 19:10 ` Jerome Brunet
2026-10-12 19:59 ` Alex Elder
2026-10-13 7:03 ` Jerome Brunet
2026-10-13 13:37 ` Alex Elder
2026-10-13 14:16 ` Jerome Brunet
2026-10-12 15:24 ` [PATCH v3 3/4] arm64: dts: qcom: define a fixed 25 MHz clock Alex Elder
2026-10-12 16:02 ` Konrad Dybcio
2026-10-12 16:04 ` Alex Elder
2026-10-12 15:24 ` [PATCH v3 4/4] arm64: dts: qcom: qcs6490-rb3gen2: add the clock controller Alex Elder
2026-10-12 16:02 ` Konrad Dybcio
2026-10-12 16:04 ` Alex Elder
2026-10-14 10:20 ` Krzysztof Kozlowski
2026-10-12 19:10 ` [PATCH v3 0/4] clk: introduce TC9564 clock support Jerome Brunet
2026-10-12 19:59 ` Alex Elder
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=f7ef8af7-e8b4-4ee5-88e2-f3271e10ea9c@kernel.org \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=daniel@riscstar.com \
--cc=danielt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@riscstar.com \
--cc=gustavoars@kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.bianconi@oss.qualcomm.com \
--cc=mohd.anwar@oss.qualcomm.com \
--cc=robh@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
all inboxes | Powered by JetHome®