From: Mark Greer <mgreer@animalcreek.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Bongsu Jeon <bongsu.jeon@samsung.com>,
Mark Greer <mgreer@animalcreek.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove the linux-nfc@lists.01.org list
Date: Tue, 28 Mar 2023 10:19:02 -0700 [thread overview]
Message-ID: <ZCMhho3Rc44TYPYz@animalcreek.com> (raw)
In-Reply-To: <eb05ac50-fda2-8324-1fd9-fda8579dfd8c@linaro.org>
On Fri, Mar 24, 2023 at 09:26:56AM +0100, Krzysztof Kozlowski wrote:
> On 24/03/2023 09:16, Lukas Bulwahn wrote:
> > Some MAINTAINERS sections mention to mail patches to the list
> > linux-nfc@lists.01.org. Probably due to changes on Intel's 01.org website
> > and servers, the list server lists.01.org/ml01.01.org is simply gone.
> >
> > Considering emails recorded on lore.kernel.org, only a handful of emails
> > where sent to the linux-nfc@lists.01.org list, and they are usually also
> > sent to the netdev mailing list as well, where they are then picked up.
> > So, there is no big benefit in restoring the linux-nfc elsewhere.
> >
> > Remove all occurrences of the linux-nfc@lists.01.org list in MAINTAINERS.
> >
> > Suggested-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Link: https://lore.kernel.org/all/CAKXUXMzggxQ43DUZZRkPMGdo5WkzgA=i14ySJUFw4kZfE5ZaZA@mail.gmail.com/
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
[Sorry, been traveling the last several days.]
Reviewed-by: Mark Greer <mgreer@animalcreek.com>
next prev parent reply other threads:[~2023-03-28 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 8:16 [PATCH] MAINTAINERS: remove the linux-nfc@lists.01.org list Lukas Bulwahn
2023-03-24 8:26 ` Krzysztof Kozlowski
2023-03-28 17:19 ` Mark Greer [this message]
2023-03-28 22:05 ` Jakub Kicinski
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=ZCMhho3Rc44TYPYz@animalcreek.com \
--to=mgreer@animalcreek.com \
--cc=bongsu.jeon@samsung.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.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