From: Boris Brezillon <boris.brezillon@collabora.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
Boris Brezillon <bbrezillon@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Mark linux-i3c mailing list moderated
Date: Fri, 15 Nov 2019 06:15:54 +0100 [thread overview]
Message-ID: <20191115061554.532d29e9@collabora.com> (raw)
In-Reply-To: <20191024153756.31861-1-geert+renesas@glider.be>
On Thu, 24 Oct 2019 17:37:56 +0200
Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> The linux-i3c mailing list is moderated for non-subscribers.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Queued to i3c/next. It was actually queued 2 weeks ago but the
patchwork bot didn't send a notification for that one (one was sent for
your other patch) and I don't know why.
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7f361fba6c4070ae..937017266a2edf08 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7746,7 +7746,7 @@ F: drivers/i2c/i2c-stub.c
>
> I3C SUBSYSTEM
> M: Boris Brezillon <bbrezillon@kernel.org>
> -L: linux-i3c@lists.infradead.org
> +L: linux-i3c@lists.infradead.org (moderated for non-subscribers)
> C: irc://chat.freenode.net/linux-i3c
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git
> S: Maintained
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2019-11-15 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 15:37 [PATCH] MAINTAINERS: Mark linux-i3c mailing list moderated Geert Uytterhoeven
2019-11-15 5:15 ` Boris Brezillon [this message]
2019-11-15 8:10 ` Geert Uytterhoeven
2019-11-15 8:40 ` Boris Brezillon
2019-11-15 8:54 ` Geert Uytterhoeven
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=20191115061554.532d29e9@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=bbrezillon@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).