From: Greg KH <gregkh@linuxfoundation.org>
To: 周寅 <zain_zhou@realsil.com.cn>
Cc: "linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"Frank.Li@nxp.com" <Frank.Li@nxp.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linusw@kernel.org" <linusw@kernel.org>,
"brgl@kernel.org" <brgl@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
王炜 <wei_wang@realsil.com.cn>
Subject: Re: 答复: [PATCH 2/2] staging: i3c: add Realtek RTS490x I3C HUB driver
Date: Mon, 25 May 2026 21:12:51 +0200 [thread overview]
Message-ID: <2026052533-flattop-carat-c489@gregkh> (raw)
In-Reply-To: <1a79b9c3c6c64e5ba65292efa2f0472f@realsil.com.cn>
On Mon, May 25, 2026 at 12:58:33PM +0000, 周寅 wrote:
> Thank you for the review.
>
> We noticed that the NXP P3H2x4x series (v10) introduces a generic
> I3C hub framework. Would you recommend waiting for that to land
> before resubmitting to the proper location?
I have no context, and do not know, why not ask the i3c maintainer?
greg k-h
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2026-05-25 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 12:13 [PATCH 1/2] dt-bindings: i3c: add binding for Realtek RTS490x I3C HUB zain_zhou
2026-04-30 12:13 ` [PATCH 2/2] staging: i3c: add Realtek RTS490x I3C HUB driver zain_zhou
2026-05-04 14:25 ` Greg KH
2026-05-25 12:58 ` 答复: " 周寅
2026-05-25 19:12 ` Greg KH [this message]
2026-04-30 13:41 ` [PATCH 1/2] dt-bindings: i3c: add binding for Realtek RTS490x I3C HUB Rob Herring (Arm)
2026-05-01 9:37 ` Krzysztof Kozlowski
2026-05-25 12:54 ` 答复: " 周寅
2026-05-04 20:34 ` Frank Li
2026-05-25 13:07 ` 答复: " 周寅
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=2026052533-flattop-carat-c489@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=robh@kernel.org \
--cc=wei_wang@realsil.com.cn \
--cc=zain_zhou@realsil.com.cn \
/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