From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-samsung-soc@vger.kernel.org,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
Pia Eichinger <pia.eichinger@st.oth-regensburg.de>,
Joe Perches <joe@perches.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: mark linux-samsung-soc list non-moderated
Date: Wed, 16 Sep 2020 19:45:55 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2009162140130.14568@felia> (raw)
In-Reply-To: <20200916165357.GA18287@kozik-lap>
On Wed, 16 Sep 2020, Krzysztof Kozlowski wrote:
> On Mon, Sep 14, 2020 at 08:13:53AM +0200, Lukas Bulwahn wrote:
> > In fifteen entries mentioning linux-samsung-soc@vger.kernel.org in
> > MAINTAINERS, seven entries mention the list being moderated for
> > non-subscribers and eight entries do not. Clearly only one can be right,
> > though.
> >
> > Joe Perches suggested that all vger.kernel.org are not moderated for
> > non-subscribers.
> >
> > Remove all the remarks from the entries following Joe's suggestion.
> >
> > Link: https://lore.kernel.org/lkml/da6f30896a8fd78635b3ca454d77a5292a9aa76d.camel@perches.com/
> > Suggested-by: Joe Perches <joe@perches.com>
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> > ---
> > applies cleanly on v5.9-rc5 and next-20200911
> >
> > Krzysztof, please pick this minor non-urgent cleanup patch.
> >
> > This patch submission will also show me if linux-samsung-soc is moderated
> > or not. I have not subscribed to linux-samsung-soc and if it shows up
> > quickly in the archive, the list is probably not moderated, and hence,
> > validating the patch.
>
> Please use scripts/get_maintainers.pl (for example on files in modified
> maintainers section) to get the addresses of people. This mail missed
> all my filters and got archived immediately because you sent it to
> unusual address (how did you get this address, BTW? It does not appear
> in the sources since few years).
>
Sorry, I usually do use ./scripts/get_maintainers.pl and you are right
there is no way one could pick up that email address from the repository.
It was difficult to recall where I got the address from, but then I
finally remembered.
I wanted to know who is responsible for the linus-samsung-soc mailing
list for this patch. So I went to:
https://patchwork.kernel.org/project/linux-samsung-soc/
And there in 'About this project', it still lists your gmail address. I
did not crosscheck that mail address with .mailmap, get_maintainers.pl
etc., but just send the patch out.
> Thanks, applied.
I am happy it reached you despite this mess-up on my side.
Lukas
next prev parent reply other threads:[~2020-09-16 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 6:13 [PATCH] MAINTAINERS: mark linux-samsung-soc list non-moderated Lukas Bulwahn
2020-09-14 6:32 ` Lukas Bulwahn
2020-09-16 16:53 ` Krzysztof Kozlowski
2020-09-16 19:45 ` Lukas Bulwahn [this message]
2020-09-17 19:46 ` Krzysztof Kozlowski
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=alpine.DEB.2.21.2009162140130.14568@felia \
--to=lukas.bulwahn@gmail.com \
--cc=joe@perches.com \
--cc=k.kozlowski.k@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pia.eichinger@st.oth-regensburg.de \
--cc=ralf.ramsauer@oth-regensburg.de \
/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).