From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-aspeed@lists.ozlabs.org, linux-clk@vger.kernel.org
Cc: devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Dylan Hung <dylan_hung@aspeedtech.com>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>
Subject: Re: [PATCH v2 3/3] dts: ast2600: Add reset config for I3C
Date: Mon, 13 Feb 2023 17:02:28 +0800 [thread overview]
Message-ID: <40269fdbc75a149a37e8a44f62cb3a6102f61d8a.camel@codeconstruct.com.au> (raw)
In-Reply-To: <4eed8885-a149-43b1-f6f6-f9b7fbb2f3b4@linaro.org>
Hi Krzysztof,
> 2. This is not DTS. There is nothing from DTS here.
[and from, your reply on patch 2/3:]
> Why do you use subject prefix in patch 1 different than in patch 2?
Ack, will change to "clk:"; there is quite a mix of "dt-bindings:" and
"clk:" on the changes within this dir. I'll unify across the series.
Cheers,
Jeremy
next prev parent reply other threads:[~2023-02-13 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 6:02 [PATCH v2 0/3] Add definitions for AST2600 i3c clocks and resets Jeremy Kerr
2023-02-13 6:02 ` [PATCH v2 1/3] clk: ast2600: allow empty entries in aspeed_g6_gates Jeremy Kerr
2023-02-13 6:02 ` [PATCH v2 2/3] clk: aspeed: Add full configs for i3c clocks Jeremy Kerr
2023-02-13 8:44 ` Krzysztof Kozlowski
2023-02-13 9:48 ` Krzysztof Kozlowski
2023-02-13 12:34 ` Jeremy Kerr
2023-02-13 6:02 ` [PATCH v2 3/3] dts: ast2600: Add reset config for I3C Jeremy Kerr
2023-02-13 8:44 ` Krzysztof Kozlowski
2023-02-13 9:02 ` Jeremy Kerr [this message]
2023-02-13 9:06 ` Krzysztof Kozlowski
2023-02-13 9:23 ` Jeremy Kerr
2023-02-13 9:31 ` Krzysztof Kozlowski
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=40269fdbc75a149a37e8a44f62cb3a6102f61d8a.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=dylan_hung@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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