From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: make linux-usb list remarks consistent
Date: Mon, 14 Sep 2020 09:08:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2009140834010.17999@felia> (raw)
In-Reply-To: <da6f30896a8fd78635b3ca454d77a5292a9aa76d.camel@perches.com>
On Sat, 12 Sep 2020, Joe Perches wrote:
> On Sat, 2020-09-12 at 14:40 +0200, Greg Kroah-Hartman wrote:
> > On Sat, Sep 12, 2020 at 02:19:02PM +0200, Lukas Bulwahn wrote:
> > >
> > > On Sat, 12 Sep 2020, Lukas Bulwahn wrote:
> > >
> > > > This patch submission will also show me if linux-usb is moderated or not.
> > > > I have not subscribed to linux-usb and if it shows up quickly in the
> > > > archive, the list is probably not moderated, and hence, validating the
> > > > patch.
> > > >
> > >
> > > The patch showed up in the archives within seconds:
> > >
> > > https://lore.kernel.org/linux-usb/20200912121346.2796-1-lukas.bulwahn@gmail.com/
> > >
> > > So, the linux-usb list is most likely not moderated. Patch validated.
> >
> > Yes, it is not moderated, and never has been, no idea where that idea came from.
>
> There's also linux-samsung-soc@vger.kernel.org
> that is listed as moderated
>
> Are any of the vger lists actually moderated?
>
Joe, I found these five list entries with inconsistent remarks:
- linux-usb@vger.kernel.org:
- Patch: https://lore.kernel.org/lkml/20200912121346.2796-1-lukas.bulwahn@gmail.com/ (the patch here)
- linux-aspeed@lists.ozlabs.org:
- Patch: https://lore.kernel.org/lkml/20200912183334.22683-1-lukas.bulwahn@gmail.com/
- linux-mediatek@lists.infradead.org:
- Patch: https://lore.kernel.org/lkml/20200914053110.23286-1-lukas.bulwahn@gmail.com/
- initial patch here was wrong.
- waiting for somebody to confirm that it is not moderated to then
send the correct patch.
- linux-samsung-soc@vger.kernel.org:
- Patch: https://lore.kernel.org/lkml/20200914061353.17535-1-lukas.bulwahn@gmail.com/
- linux-arm-kernel@lists.infradead.org:
- by 'majority vote' (131 vs. 27), it is probably moderated.
- no patch sent yet; patch will follow once the others are accepted.
Then, more patches on adding 'exploders for non-subscribers' remarks will
follow.
Lukas
prev parent reply other threads:[~2020-09-14 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 12:13 Lukas Bulwahn
2020-09-12 12:19 ` Lukas Bulwahn
2020-09-12 12:40 ` Greg Kroah-Hartman
2020-09-12 15:25 ` Joe Perches
2020-09-14 7:08 ` Lukas Bulwahn [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=alpine.DEB.2.21.2009140834010.17999@felia \
--to=lukas.bulwahn@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@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
all inboxes | Powered by JetHome®