From: Randy Dunlap <rdunlap@infradead.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
James Bottomley <jejb@linux.ibm.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Mimi Zohar <zohar@linuxibm.com>
Cc: linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: use tab instead of spaces
Date: Sun, 10 Feb 2019 10:21:42 -0800 [thread overview]
Message-ID: <f34543f5-d0fc-b998-9ce1-c8f3fd36db73@infradead.org> (raw)
In-Reply-To: <20190210181011.6117-1-lukas.bulwahn@gmail.com>
On 2/10/19 10:10 AM, Lukas Bulwahn wrote:
> Mimi Zohar used spaces instead of a tab when adding Jarkko Sakkinen as
> further maintainer to the KEYS-TRUSTED section entry. So, we rectify this
> with this commit.
>
> The issue was detected when writing a script that parses MAINTAINERS.
>
> Fixes: 34bccd61b139 ("MAINTAINERS: add Jarkko as maintainer for trusted keys")
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Mimi, please pick up this patch. Thanks.
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index bf4965d6d5de..31950caabcaf 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8405,7 +8405,7 @@ F: security/keys/encrypted-keys/
>
> KEYS-TRUSTED
> M: James Bottomley <jejb@linux.ibm.com>
> -M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> +M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> M: Mimi Zohar <zohar@linuxibm.com>
Just checking: is that email address correct (@linuxibm.com)?
Guess I'll see if it bounces.
> L: linux-integrity@vger.kernel.org
> L: keyrings@vger.kernel.org
>
--
~Randy
next prev parent reply other threads:[~2019-02-10 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 18:10 [PATCH] MAINTAINERS: use tab instead of spaces Lukas Bulwahn
2019-02-10 18:21 ` Randy Dunlap [this message]
2019-02-10 18:30 ` Lukas Bulwahn
2019-02-10 18:25 ` James Bottomley
2019-02-10 19:06 ` lukas.bulwahn
2019-02-11 2:21 ` Joe Perches
2019-02-11 1:54 ` Joe Perches
2019-02-11 15:14 ` Lukas Bulwahn
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=f34543f5-d0fc-b998-9ce1-c8f3fd36db73@infradead.org \
--to=rdunlap@infradead.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=zohar@linuxibm.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).