From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-aspeed@lists.ozlabs.org, David Airlie <airlied@linux.ie>,
kernel-janitors@vger.kernel.org,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Joel Stanley <joel@jms.id.au>, Joe Perches <joe@perches.com>,
Pia Eichinger <pia.eichinger@st.oth-regensburg.de>
Subject: Re: [PATCH] MAINTAINERS: make linux-aspeed list remarks consistent
Date: Sun, 13 Sep 2020 09:57:01 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2009131156090.6163@felia> (raw)
In-Reply-To: <20200912183334.22683-1-lukas.bulwahn@gmail.com>
On Sat, 12 Sep 2020, Lukas Bulwahn wrote:
> Commit f15a3ea80391 ("MAINTAINERS: Add ASPEED BMC GFX DRM driver entry")
> does not mention that linux-aspeed@lists.ozlabs.org is moderated for
> non-subscribers, but the other three entries for
> linux-aspeed@lists.ozlabs.org do.
>
> By 'majority vote' among entries, let us assume it was just missed here and
> adjust it to be consistent with others.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> applies cleanly on master and next-20200911
>
> Joel, please ack.
> David, Daniel, please pick this minor non-urgent clean-up patch.
>
> This patch submission will also show me if linux-aspeed is moderated or
> not. I have not subscribed to linux-aspeed 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 did quickly get back an moderation email that my email is being held
back. So, that response validates my patch.
Lukas
next prev parent reply other threads:[~2020-09-13 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 18:33 [PATCH] MAINTAINERS: make linux-aspeed list remarks consistent Lukas Bulwahn
2020-09-13 9:57 ` Lukas Bulwahn [this message]
2020-09-14 12:25 ` Joel Stanley
2020-09-16 9:19 ` Daniel Vetter
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.2009131156090.6163@felia \
--to=lukas.bulwahn@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=joel@jms.id.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@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).