From: Andrew Lunn <andrew@lunn.ch>
To: Aisheng Dong <aisheng.dong@nxp.com>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"dongas86@gmail.com" <dongas86@gmail.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
Frank Li <frank.li@nxp.com>,
"kernel@dh-electronics.com" <kernel@dh-electronics.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux@ew.tq-group.com" <linux@ew.tq-group.com>
Subject: Re: [PATCH 1/1] arm64: dts: imx8mp: Update pin function file according to Rev.D RM
Date: Tue, 25 Nov 2025 01:15:14 +0100 [thread overview]
Message-ID: <10502960-d426-49fb-aabf-dc62f11153e1@lunn.ch> (raw)
In-Reply-To: <DU0PR04MB9299811B113C555FD795FDC280D0A@DU0PR04MB9299.eurprd04.prod.outlook.com>
> But how about the remain changes (drop invalid defines and adding new ones)?
You should probably make these separate patches, with good commit
messages why the are invalid, and what the new ones are useful for.
Andrew
prev parent reply other threads:[~2025-11-25 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 9:54 [PATCH 1/1] arm64: dts: imx8mp: Update pin function file according to Rev.D RM Dong Aisheng
2025-11-24 11:11 ` Alexander Stein
2025-11-24 13:46 ` Aisheng Dong
2025-11-24 13:56 ` Alexander Stein
2025-11-24 12:07 ` Ahmad Fatoum
2025-11-24 13:39 ` Aisheng Dong
2025-11-24 13:54 ` Ahmad Fatoum
2025-11-24 15:08 ` Aisheng Dong
2025-11-24 15:19 ` Ahmad Fatoum
2025-11-25 0:15 ` Andrew Lunn [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=10502960-d426-49fb-aabf-dc62f11153e1@lunn.ch \
--to=andrew@lunn.ch \
--cc=a.fatoum@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=dongas86@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@ew.tq-group.com \
--cc=robh@kernel.org \
--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