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



On 14/09/2020 12:20, Lukas Bulwahn wrote:
> 
> 
> On Mon, 14 Sep 2020, Matthias Brugger wrote:
> 
>>
>>
>> On 14/09/2020 07:31, Lukas Bulwahn wrote:
>>> Commit 637cfacae96f ("PCI: mediatek: Add MediaTek PCIe host controller
>>> support") does not mention that linux-mediatek@lists.infradead.org is
>>> moderated for non-subscribers, but the other eight entries for
>>> linux-mediatek@lists.infradead.org do.
>>>
>>> Adjust this entry to be consistent with all others.
>>>
>>> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>>
>> Maybe rephrase the commit message to something like:
>> "Mark linux-mediatek@lists.infraded.org as moderated for the MediaTek PCIe
>> host controller entry, as the list actually is moderated."
>>
>> Anyway:
>> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
>>
>>> ---
>>> applies cleanly on v5.9-rc5 and next-20200911
>>>
>>> Ryder, please ack.
>>>
>>> Bjorn, Matthias, please pick this minor non-urgent clean-up patch.
>>>
>>> This patch submission will also show me if linux-mediatek is moderated or
>>> not. I have not subscribed to linux-mediatek and if it shows up quickly in
>>> the archive, the list is probably not moderated; and if it takes longer, it
>>> is moderated, and hence, validating the patch.
>>
>> I can affirm the list is moderated :)
>>
> 
> Hmm, do we mean the same "moderation" here?
> 
> I believe a mailing list with the remark "moderated for non-subscribers"
> means that a mail from an address that has not subscribed to the mailing
> list is put on hold and needs to be manually permitted to be seen on the
> mailing list.
> 
> Matthias, is that also your understanding of "moderated for
> non-subscribers" for your Reviewed-by tag?

Yes.

> 
> I am not subscribed to linux-mediatek. When I sent an email to the list,
> it showed up really seconds later in the lore.kernel.org of the
> linux-mediatek public-inbox repository. So, either it was delivered
> quickly as it is not moderated or my check with lore.kernel.org is wrong,
> e.g., mails show up in the lore.kernel.org archive, even they were not
> yet permitted on the actual list.
> 

I'm the moderator and I get requests to moderate emails. I suppose I added you 
to the accepted list because of earlier emails you send.

Regards,
Matthias

  reply	other threads:[~2020-09-14 13:11 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 [this message]
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
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=9c5aaa15-bdd8-ae4f-0642-092566ab08ba@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=bhelgaas@google.com \
    --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=lukas.bulwahn@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).