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 v3 5/5] dt-bindings: clock: ast2600: Add reset config for I3C
Date: Mon, 13 Feb 2023 14:44:09 +0100 [thread overview]
Message-ID: <eb0fa8ee-9c14-c8a4-2d3e-6180f5d875b6@linaro.org> (raw)
In-Reply-To: <3aad8dc671a65e65f0cced648847c504514f5b0e.1676294433.git.jk@codeconstruct.com.au>
On 13/02/2023 14:24, Jeremy Kerr wrote:
> Add reset line definitions for the AST2600 I3C block's reset inputs.
>
> Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
prev parent reply other threads:[~2023-02-13 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 13:24 [PATCH v3 0/5] Add definitions for AST2600 i3c clocks and resets Jeremy Kerr
2023-02-13 13:24 ` [PATCH v3 1/5] clk: ast2600: allow empty entries in aspeed_g6_gates Jeremy Kerr
2023-02-13 13:24 ` [PATCH v3 2/5] dt-bindings: clock: ast2600: Add top-level I3C clock Jeremy Kerr
2023-02-13 13:42 ` Krzysztof Kozlowski
2023-02-13 13:24 ` [PATCH v3 3/5] clk: ast2600: Add full configs for I3C clocks Jeremy Kerr
2023-02-13 13:24 ` [PATCH v3 4/5] dt-bindings: clock: ast2600: remove IC36 & I3C7 clock definitions Jeremy Kerr
2023-02-13 13:43 ` Krzysztof Kozlowski
2023-02-13 13:24 ` [PATCH v3 5/5] dt-bindings: clock: ast2600: Add reset config for I3C Jeremy Kerr
2023-02-13 13:44 ` 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=eb0fa8ee-9c14-c8a4-2d3e-6180f5d875b6@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