From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: linux-i3c@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Boris Brezillon <bbrezillon@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Mark linux-i3c mailing list moderated
Date: Fri, 15 Nov 2019 09:54:15 +0100 [thread overview]
Message-ID: <CAMuHMdVvycHZv6g-vem7Mu4fqVc9FBx2xrdER85Sjb+vVW0=sA@mail.gmail.com> (raw)
In-Reply-To: <20191115094010.31acadf6@collabora.com>
Hi Boris,
On Fri, Nov 15, 2019 at 9:40 AM Boris Brezillon
<boris.brezillon@collabora.com> wrote:
> On Fri, 15 Nov 2019 09:10:02 +0100
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> > Hi Boris,
> >
> > On Fri, Nov 15, 2019 at 6:16 AM Boris Brezillon
> > <boris.brezillon@collabora.com> wrote:
> > > 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.
> >
> > It did:
>
> Ok, perfect then. Looks like sometimes it doesn't work, but for this
> patch I did receive a notification too (it was one notification for both
> of your patches and I thought I was receiving one per patch).
It is one per patch, I did receive the other one, too:
Subject: Re: [PATCH trivial] i3c: Spelling s/dicovered/discovered/
From: patchwork-bot+linux-i3c@kernel.org
Message-Id: <157251967168.27046.5733392327207757366.git-patchwork-notify@kernel.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2019-11-15 10:48 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
2019-11-15 8:10 ` Geert Uytterhoeven
2019-11-15 8:40 ` Boris Brezillon
2019-11-15 8:54 ` Geert Uytterhoeven [this message]
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='CAMuHMdVvycHZv6g-vem7Mu4fqVc9FBx2xrdER85Sjb+vVW0=sA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--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).