From: Shawn Guo <shawnguo2@yeah.net>
To: carlos.song@nxp.com
Cc: miquel.raynal@bootlin.com, Frank.Li@nxp.com,
alexandre.belloni@bootlin.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, conor.culhane@silvaco.com,
linux-i3c@lists.infradead.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 3/3] arm64: dts: imx95: correct i3c node in imx95
Date: Wed, 11 Jun 2025 16:28:04 +0800 [thread overview]
Message-ID: <aEk+FEq+Ivj5wfVW@dragon> (raw)
In-Reply-To: <20250427083230.3325700-4-carlos.song@nxp.com>
On Sun, Apr 27, 2025 at 04:32:30PM +0800, carlos.song@nxp.com wrote:
> From: Carlos Song <carlos.song@nxp.com>
>
> I.MX95 I3C only need two clocks so add clock fix. Add "nxp,imx95-i3c"
> compatible string for all imx95 i3c nodes.
>
> Signed-off-by: Carlos Song <carlos.song@nxp.com>
Applied, thanks!
next prev parent reply other threads:[~2025-06-11 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 8:32 [PATCH V4 0/3] support different number of clocks for svc i3c controller carlos.song
2025-04-27 8:32 ` [PATCH V4 1/3] dt-bindings: i3c: silvaco,i3c-master: add i.MX94 and i.MX95 I3C carlos.song
2025-04-28 6:59 ` Krzysztof Kozlowski
2025-04-27 8:32 ` [PATCH V4 2/3] i3c: master: svc: switch to bulk clk API for flexible clock support carlos.song
2025-04-27 8:32 ` [PATCH V4 3/3] arm64: dts: imx95: correct i3c node in imx95 carlos.song
2025-05-14 2:04 ` Carlos Song
2025-06-11 8:28 ` Shawn Guo [this message]
2025-05-24 20:51 ` (subset) [PATCH V4 0/3] support different number of clocks for svc i3c controller Alexandre Belloni
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=aEk+FEq+Ivj5wfVW@dragon \
--to=shawnguo2@yeah.net \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=carlos.song@nxp.com \
--cc=conor+dt@kernel.org \
--cc=conor.culhane@silvaco.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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