linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: paulmck@linux.ibm.com, Baruch Siach <baruch@tkos.co.il>
Cc: linux-integrity@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: fix typo in Mimi Zohar's address
Date: Thu, 07 Mar 2019 09:26:56 -0500	[thread overview]
Message-ID: <1551968816.31706.336.camel@linux.ibm.com> (raw)
In-Reply-To: <20190307141957.GO13351@linux.ibm.com>

On Thu, 2019-03-07 at 06:19 -0800, Paul E. McKenney wrote:
> On Thu, Mar 07, 2019 at 07:36:39AM +0200, Baruch Siach wrote:
> > Hi Paul,
> > 
> > On Thu, Dec 27 2018, Paul E. McKenney wrote:
> > 
> > > On Thu, Dec 27, 2018 at 07:50:49AM +0200, Baruch Siach wrote:
> > >> Fixes: ("MAINTAINERS: Update from @linux.vnet.ibm.com to @linux.ibm.com")
> > >> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > >
> > > Reviewed-by: Paul E. McKenney <paulmck@linux.ibm.com>
> > >
> > > And where is a brown paper bag when you need one?  :-/
> > 
> > This has missed v5.0.
> 
> And v5.1 unless someone is pushing it into this merge window.
> 
> > Which tree is this patch supposed to go through, anyway?
> 
> I was expecting you to push it somewhere, hence my Reviewed-by.  But I
> can take it, and if I do it will be v5.2.

I'm really sorry I missed that.
> 
> Or you could try sending it directly to Linus, which would very likely
> get it into v5.1.

If you decide not to send it, I'll include it for v5.2.

Mimi


      reply	other threads:[~2019-03-07 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27  5:50 [PATCH] MAINTAINERS: fix typo in Mimi Zohar's address Baruch Siach
2018-12-27 16:53 ` Paul E. McKenney
     [not found]   ` <87r2bj2ql4.fsf@tarshish>
2019-03-07 14:19     ` Paul E. McKenney
2019-03-07 14:26       ` Mimi Zohar [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=1551968816.31706.336.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=baruch@tkos.co.il \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=paulmck@linux.ibm.com \
    /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).