kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Ryder Lee <ryder.lee@mediatek.com>, Joe Perches <joe@perches.com>,
	linux-pci@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
	linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Pia Eichinger <pia.eichinger@st.oth-regensburg.de>
Subject: Re: [PATCH] MAINTAINERS: make linux-mediatek list remarks consistent
Date: Mon, 14 Sep 2020 15:23:58 +0000	[thread overview]
Message-ID: <alpine.DEB.2.21.2009141717470.17999@felia> (raw)
In-Reply-To: <f511570405799df421397ff65847e927745dad08.camel@infradead.org>



On Mon, 14 Sep 2020, David Woodhouse wrote:

> On Mon, 2020-09-14 at 16:57 +0200, Lukas Bulwahn wrote:
> > Well, I am happy to send any PATCH v2. I guess we, you, David, Matthias 
> > and I, now just need to determine if the list is moderated or not.
> 
> It really isn't.
> 
>  # /usr/lib/mailman/bin/config_list -o- linux-mediatek | grep -B5 ^generic_nonmember_action
> # legal values are:
> #    0 = "Accept"
> #    1 = "Hold"
> #    2 = "Reject"
> #    3 = "Discard"
> generic_nonmember_action = 0
> 

David, I guess if you have access to the ground truth on 
lists.infradead.org, maybe you can dump the actual setting for all those 
lists?

$ grep "lists.infradead.org" MAINTAINERS | sort | uniq

L:	ath10k@lists.infradead.org
L:	ath11k@lists.infradead.org
L:	b43-dev@lists.infradead.org
L:	kexec@lists.infradead.org
L:	libertas-dev@lists.infradead.org
L:	linux-afs@lists.infradead.org
L:	linux-amlogic@lists.infradead.org
L:	linux-arm-kernel@lists.infradead.org
L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
L:	linux-geode@lists.infradead.org (moderated for non-subscribers)
L:	linux-i3c@lists.infradead.org (moderated for non-subscribers)
L:	linux-mediatek@lists.infradead.org
L:	linux-mediatek@lists.infradead.org (moderated for non-subscribers)
L:	linux-mtd@lists.infradead.org
L:	linux-nvme@lists.infradead.org
L:	linux-parport@lists.infradead.org (subscribers-only)
L:	linux-realtek-soc@lists.infradead.org (moderated for non-subscribers)
L:	linux-riscv@lists.infradead.org
L:	linux-rockchip@lists.infradead.org
L:	linux-rpi-kernel@lists.infradead.org (moderated for non-subscribers)
L:	linux-snps-arc@lists.infradead.org
L:	linux-um@lists.infradead.org
L:	linux-unisoc@lists.infradead.org (moderated for non-subscribers)
L:	wcn36xx@lists.infradead.org


They are all reporting different settings and linux-mediatek and 
linux-arm-kernel even inconsistently. The inconsistency and a poor attempt 
to resolve that is what started this discussion.

I can then send out the patch to adjust MAINTAINERS to your ground truth 
from the server.

Thanks for your support,

Lukas

  reply	other threads:[~2020-09-14 15:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  5:31 [PATCH] MAINTAINERS: make linux-mediatek list remarks consistent Lukas Bulwahn
2020-09-14  5:39 ` Lukas Bulwahn
2020-09-14  9:25 ` Matthias Brugger
2020-09-14 10:20   ` Lukas Bulwahn
2020-09-14 13:11     ` Matthias Brugger
2020-09-14 14:01       ` Lukas Bulwahn
2020-09-14 14:12         ` David Woodhouse
2020-09-14 14:57           ` Lukas Bulwahn
2020-09-14 15:16             ` David Woodhouse
2020-09-14 15:23               ` Lukas Bulwahn [this message]
2020-09-14 15:30                 ` David Woodhouse
2020-09-14 15:31                   ` Lukas Bulwahn
2020-09-14 15:17           ` Lukas Bulwahn
2020-09-15  8:41           ` Matthias Brugger

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.2009141717470.17999@felia \
    --to=lukas.bulwahn@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dwmw2@infradead.org \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=pia.eichinger@st.oth-regensburg.de \
    --cc=ralf.ramsauer@oth-regensburg.de \
    --cc=ryder.lee@mediatek.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 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).