From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] MAINTAINERS: make linux-aspeed list remarks consistent
Date: Sat, 12 Sep 2020 20:33:34 +0200 [thread overview]
Message-ID: <20200912183334.22683-1-lukas.bulwahn@gmail.com> (raw)
Commit f15a3ea80391 ("MAINTAINERS: Add ASPEED BMC GFX DRM driver entry")
does not mention that linux-aspeed at lists.ozlabs.org is moderated for
non-subscribers, but the other three entries for
linux-aspeed at 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.
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 26af84f97353..f2561c3fc9db 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5448,7 +5448,7 @@ F: drivers/gpu/drm/panel/panel-arm-versatile.c
DRM DRIVER FOR ASPEED BMC GFX
M: Joel Stanley <joel@jms.id.au>
-L: linux-aspeed at lists.ozlabs.org
+L: linux-aspeed at lists.ozlabs.org (moderated for non-subscribers)
S: Supported
T: git git://anongit.freedesktop.org/drm/drm-misc
F: Documentation/devicetree/bindings/gpu/aspeed-gfx.txt
--
2.17.1
next reply other threads:[~2020-09-12 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 18:33 Lukas Bulwahn [this message]
2020-09-13 9:57 ` [PATCH] MAINTAINERS: make linux-aspeed list remarks consistent Lukas Bulwahn
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=20200912183334.22683-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=linux-aspeed@lists.ozlabs.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