From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jeremy Kerr <jk@codeconstruct.com.au>,
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 10:31:23 +0100 [thread overview]
Message-ID: <1ab0b28d-8935-4e4c-ba8a-635de1f5bb8d@linaro.org> (raw)
In-Reply-To: <34b2ebb4781c6157496012efce392743e1821c8a.camel@codeconstruct.com.au>
On 13/02/2023 10:23, Jeremy Kerr wrote:
> Hi Krzysztof,
>
>> There was clk already, wasn't it? What do you want to change?
>> I asked why do you call it in the same patchset aspeed and as2600?
>
> There was "clk" and "dts",
In patch 1 and 2? Please point me.
> where the latter should have probably been either
> also "clk" or "dt-bindings".
Aren't you referring to some other comment now?
>
> I'll unify the "aspeed" to "ast2600".
>
> Cheers,
>
>
> Jeremy
Best regards,
Krzysztof
prev parent reply other threads:[~2023-02-13 9:33 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
2023-02-13 9:06 ` Krzysztof Kozlowski
2023-02-13 9:23 ` Jeremy Kerr
2023-02-13 9:31 ` Krzysztof Kozlowski [this message]
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=1ab0b28d-8935-4e4c-ba8a-635de1f5bb8d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=dylan_hung@aspeedtech.com \
--cc=jk@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@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