From: Aisheng Dong <aisheng.dong@nxp.com>
To: "Daniel Baluta (OSS)" <daniel.baluta@oss.nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>
Cc: "kernel@pengutronix.de" <kernel@pengutronix.de>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"abel.vesa@linaro.org" <abel.vesa@linaro.org>,
Bough Chen <haibo.chen@nxp.com>, Peng Fan <peng.fan@nxp.com>,
"S.J. Wang" <shengjiu.wang@nxp.com>, Frank Li <frank.li@nxp.com>,
Laurentiu Palcu <laurentiu.palcu@nxp.com>,
Mirela Rabulea <mirela.rabulea@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>
Subject: RE: [PATCH] MAINTAINERS: Use a proper mailinglist for NXP i.MX development
Date: Thu, 22 Feb 2024 08:53:41 +0000 [thread overview]
Message-ID: <DU0PR04MB929999670DBEBD38C031788280562@DU0PR04MB9299.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20240220164005.1345603-1-daniel.baluta@oss.nxp.com>
> From: Daniel Baluta (OSS) <daniel.baluta@oss.nxp.com>
> Sent: 2024年2月21日 0:40
>
> So far we used an internal linux-imx@nxp.com email address to gather all
> patches related to NXP i.MX development.
>
> Let's switch to an open mailing list that provides ability for people from the
> community to subscribe and also have a proper archive.
>
> List interface at: https://lists.linux.dev.
> Archive is at: https://lore.kernel.org/imx/
>
> Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
> ---
>
> Shawn, can you please pick this up via your tree?
>
> MAINTAINERS | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8d1052fa6a69..3db382dc8f7b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2156,7 +2156,7 @@ M: Shawn Guo <shawnguo@kernel.org>
> M: Sascha Hauer <s.hauer@pengutronix.de>
> R: Pengutronix Kernel Team <kernel@pengutronix.de>
> R: Fabio Estevam <festevam@gmail.com>
> -R: NXP Linux Team <linux-imx@nxp.com>
> +R: NXP Linux Team <imx@lists.linux.dev>
Do we really need keep "NXP Linux Team" as this is actually an open list?
Otherwise, it looks good to me.
Regards
Aisheng
prev parent reply other threads:[~2024-02-22 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 16:40 [PATCH] MAINTAINERS: Use a proper mailinglist for NXP i.MX development Daniel Baluta (OSS)
2024-02-20 17:37 ` Ahmad Fatoum
2024-02-22 8:27 ` Daniel Baluta
2024-02-20 23:23 ` Peng Fan
2024-02-22 8:53 ` Aisheng Dong [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=DU0PR04MB929999670DBEBD38C031788280562@DU0PR04MB9299.eurprd04.prod.outlook.com \
--to=aisheng.dong@nxp.com \
--cc=abel.vesa@linaro.org \
--cc=daniel.baluta@nxp.com \
--cc=daniel.baluta@oss.nxp.com \
--cc=f.fainelli@gmail.com \
--cc=frank.li@nxp.com \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=laurentiu.palcu@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirela.rabulea@nxp.com \
--cc=peng.fan@nxp.com \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.