From: Shawn Guo <shawnguo2@yeah.net>
To: Peng Fan <peng.fan@nxp.com>
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: Update i.MX entry
Date: Tue, 8 Jul 2025 14:53:34 +0800 [thread overview]
Message-ID: <aGzAbk8dYliAfCrn@dragon> (raw)
In-Reply-To: <20250707063753.1684144-1-peng.fan@nxp.com>
On Mon, Jul 07, 2025 at 02:37:53PM +0800, Peng Fan wrote:
> Add two patterns:
> - Documentation/devicetree/bindings/firmware/fsl*
> - Documentation/devicetree/bindings/firmware/nxp*
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
Applied, thanks!
prev parent reply other threads:[~2025-07-08 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 6:37 [PATCH] MAINTAINERS: Update i.MX entry Peng Fan
2025-07-08 6:53 ` Shawn Guo [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=aGzAbk8dYliAfCrn@dragon \
--to=shawnguo2@yeah.net \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--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;
as well as URLs for NNTP newsgroup(s).