From: Jisheng Zhang <jszhang@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-i3c@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] dt-bindings: i3c: dw: Describe core reset
Date: Wed, 20 May 2026 19:50:44 +0800 [thread overview]
Message-ID: <ag2gFB0BSCVUCVg9@xhacker> (raw)
In-Reply-To: <20260520-cocky-thick-wren-900aa0@quoll>
On Wed, May 20, 2026 at 09:14:44AM +0200, Krzysztof Kozlowski wrote:
> On Tue, May 19, 2026 at 01:51:03PM +0800, Jisheng Zhang wrote:
> > The core reset support has been in the code from day1, but the
>
> Well, no. There was no "core" reset from day1, so your entire
aha, by "core reset" I mean the reset signal for i3c core. Not the
reset name. But I will update the commit msg.
> explanation makes no sense now. Previous version was correct.
>
OK, so I will send v4.
next prev parent reply other threads:[~2026-05-20 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 5:51 [PATCH v3 0/4] i3c: dw: Add apb reset support Jisheng Zhang
2026-05-19 5:51 ` [PATCH v3 1/4] i3c: dw: Remove core reset "_rst" suffix Jisheng Zhang
2026-05-20 7:13 ` Krzysztof Kozlowski
2026-05-20 11:43 ` Jisheng Zhang
2026-05-19 5:51 ` [PATCH v3 2/4] dt-bindings: i3c: dw: Describe core reset Jisheng Zhang
2026-05-20 7:14 ` Krzysztof Kozlowski
2026-05-20 11:50 ` Jisheng Zhang [this message]
2026-05-19 5:51 ` [PATCH v3 3/4] dt-bindings: i3c: dw: Add apb reset Jisheng Zhang
2026-05-19 6:48 ` sashiko-bot
2026-05-19 5:51 ` [PATCH v3 4/4] i3c: dw: Add apb reset support Jisheng Zhang
2026-05-19 6:58 ` sashiko-bot
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=ag2gFB0BSCVUCVg9@xhacker \
--to=jszhang@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@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