linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Boris Brezillon <bbrezillon@kernel.org>,
	linux-i3c@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Mark linux-i3c mailing list moderated
Date: Fri, 15 Nov 2019 09:40:10 +0100	[thread overview]
Message-ID: <20191115094010.31acadf6@collabora.com> (raw)
In-Reply-To: <CAMuHMdWO=8sHn9wrEiuBGes0x_L2=Qkou=aPcHM7Mr9oDS74Qw@mail.gmail.com>

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).

> 
> -----8<-----------------------------------------------------------------------------------------
> Subject: Re: [PATCH] MAINTAINERS: Mark linux-i3c mailing list moderated
> From: patchwork-bot+linux-i3c@kernel.org
> Message-Id: <157251967150.27046.1691850610457130750.git-patchwork-notify@kernel.org>
> Date: Thu, 31 Oct 2019 11:01:11 +0000
> References: <20191024153756.31861-1-geert+renesas@glider.be>
> In-Reply-To: <20191024153756.31861-1-geert+renesas@glider.be>
> To: Geert Uytterhoeven <geert+renesas@glider.be>
> X-GND-Status: LEGIT
> Received-SPF: pass (spool2: domain of kernel.org designates
> 198.145.29.99 as permitted sender) client-ip=198.145.29.99;
> envelope-from=patchwork-bot+linux-i3c@kernel.org;
> helo=mail.kernel.org;
> 
> Hello:
> 
> This patch was applied to i3c/linux.git (refs/heads/i3c/next).
> 
> On Thu, 24 Oct 2019 17:37:56 +0200 you wrote:
> > The linux-i3c mailing list is moderated for non-subscribers.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > ---
> >  MAINTAINERS | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)  
> 
> 
> Here is a summary with links:
>   - MAINTAINERS: Mark linux-i3c mailing list moderated
>     https://git.kernel.org/i3c/c/469191c7fcd069a500c2a26c49c9baef9dabf66d
> 
> You are awesome, thank you!
> 


  reply	other threads:[~2019-11-15  8:40 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 [this message]
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=20191115094010.31acadf6@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=bbrezillon@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --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).