From: Daniel Baluta <daniel.baluta@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "Daniel Baluta (OSS)" <daniel.baluta@oss.nxp.com>,
shawnguo@kernel.org, aisheng.dong@nxp.com, peng.fan@nxp.com,
f.fainelli@gmail.com, Daniel Baluta <daniel.baluta@nxp.com>,
shengjiu.wang@nxp.com, Frank.Li@nxp.com,
linux-kernel@vger.kernel.org, haibo.chen@nxp.com,
mirela.rabulea@nxp.com, kernel@pengutronix.de, kuba@kernel.org,
abel.vesa@linaro.org, laurentiu.palcu@nxp.com
Subject: Re: [PATCH] MAINTAINERS: Use a proper mailinglist for NXP i.MX development
Date: Thu, 22 Feb 2024 10:27:13 +0200 [thread overview]
Message-ID: <CAEnQRZBD1+5JbFWCguL2U7-me6gEta_-XuUZQ3GkDq9=Wck8LA@mail.gmail.com> (raw)
In-Reply-To: <05b7bf7f-9b5d-4ae3-a295-82f2b46abb4a@pengutronix.de>
On Tue, Feb 20, 2024 at 7:38 PM Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>
> Hello Daniel,
>
> On 20.02.24 17:40, Daniel Baluta (OSS) wrote:
> > From: Daniel Baluta <daniel.baluta@nxp.com>
> >
> > 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/
>
> I think the R: should be changed to L: then?
Correct. Will change it in v2.
next prev parent reply other threads:[~2024-02-22 8:27 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 [this message]
2024-02-20 23:23 ` Peng Fan
2024-02-22 8:53 ` Aisheng Dong
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='CAEnQRZBD1+5JbFWCguL2U7-me6gEta_-XuUZQ3GkDq9=Wck8LA@mail.gmail.com' \
--to=daniel.baluta@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=a.fatoum@pengutronix.de \
--cc=abel.vesa@linaro.org \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=daniel.baluta@oss.nxp.com \
--cc=f.fainelli@gmail.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.