From: Linus Walleij <linusw@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>, Jacky Bai <ping.bai@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP S32 Linux Team <s32@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: pinctrl: imx35: add compatible string fsl,imx25-iomuxc
Date: Tue, 24 Feb 2026 10:02:28 +0100 [thread overview]
Message-ID: <CAD++jLmPRLy1iJWRtfpS-7OS2533AY42OU87U6hUT59efz-B8A@mail.gmail.com> (raw)
In-Reply-To: <20260211-imx2_iomux_warning-v1-2-1c5233771b32@nxp.com>
On Wed, Feb 11, 2026 at 10:00 PM Frank Li <Frank.Li@nxp.com> wrote:
> Add compatible string fsl,imx25-iomuxc.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
This patch (2/4) applied to the pinctrl tree.
Yours,
Linus Walleij
next prev parent reply other threads:[~2026-02-24 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 20:59 [PATCH 0/4] ARM: dts: imx: cleanup iomux related CHECK_DTBS warnings for imx1, imx25 and imx27 Frank Li
2026-02-11 21:00 ` [PATCH 1/4] dt-bindings: pinctrl: convert fsl,imx27-pinctrl.txt to YAML Frank Li
2026-02-18 18:39 ` Rob Herring
2026-02-24 9:02 ` Linus Walleij
2026-02-11 21:00 ` [PATCH 2/4] dt-bindings: pinctrl: imx35: add compatible string fsl,imx25-iomuxc Frank Li
2026-02-12 11:45 ` Krzysztof Kozlowski
2026-02-24 9:02 ` Linus Walleij [this message]
2026-02-11 21:00 ` [PATCH 3/4] ARM: dts: imx: rename iomuxc to pinmux Frank Li
2026-02-11 21:00 ` [PATCH 4/4] ARM: dts: imx: remove redundant intermediate node in pinmux hierarchy Frank Li
2026-03-02 16:44 ` (subset) [PATCH 0/4] ARM: dts: imx: cleanup iomux related CHECK_DTBS warnings for imx1, imx25 and imx27 Frank Li
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=CAD++jLmPRLy1iJWRtfpS-7OS2533AY42OU87U6hUT59efz-B8A@mail.gmail.com \
--to=linusw@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--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-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ping.bai@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
/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
all inboxes | Powered by JetHome®