All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	linux-integrity@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: fix typo in Mimi Zohar's address
Date: Thu, 27 Dec 2018 16:53:04 +0000	[thread overview]
Message-ID: <20181227165304.GA4170@linux.ibm.com> (raw)
In-Reply-To: <e186bbae367ceb7a2a71e2dea216838ac19dee8f.1545889849.git.baruch@tkos.co.il>

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?  :-/

> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 705555d9b3af..0b8b0d60833a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8339,7 +8339,7 @@ F:	security/keys/encrypted-keys/
>  KEYS-TRUSTED
>  M:	James Bottomley <jejb@linux.ibm.com>
>  M:      Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> -M:	Mimi Zohar <zohar@linuxibm.com>
> +M:	Mimi Zohar <zohar@linux.ibm.com>
>  L:	linux-integrity@vger.kernel.org
>  L:	keyrings@vger.kernel.org
>  S:	Supported
> -- 
> 2.19.2
> 

WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	linux-integrity@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: fix typo in Mimi Zohar's address
Date: Thu, 27 Dec 2018 08:53:04 -0800	[thread overview]
Message-ID: <20181227165304.GA4170@linux.ibm.com> (raw)
In-Reply-To: <e186bbae367ceb7a2a71e2dea216838ac19dee8f.1545889849.git.baruch@tkos.co.il>

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?  :-/

> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 705555d9b3af..0b8b0d60833a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8339,7 +8339,7 @@ F:	security/keys/encrypted-keys/
>  KEYS-TRUSTED
>  M:	James Bottomley <jejb@linux.ibm.com>
>  M:      Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> -M:	Mimi Zohar <zohar@linuxibm.com>
> +M:	Mimi Zohar <zohar@linux.ibm.com>
>  L:	linux-integrity@vger.kernel.org
>  L:	keyrings@vger.kernel.org
>  S:	Supported
> -- 
> 2.19.2
> 


  reply	other threads:[~2018-12-27 16:53 UTC|newest]

Thread overview: 8+ 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  5:50 ` Baruch Siach
2018-12-27 16:53 ` Paul E. McKenney [this message]
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:19       ` Paul E. McKenney
2019-03-07 14:26       ` Mimi Zohar
2019-03-07 14:26         ` Mimi Zohar

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=20181227165304.GA4170@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=baruch@tkos.co.il \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=zohar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.