From: Lukas Bulwahn <lukas.bulwahn@gmail.com> To: James Bottomley <jejb@linux.ibm.com>, Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>, Mimi Zohar <zohar@linuxibm.com> Cc: paulmck@linux.vnet.ibm.com, linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org, Lukas Bulwahn <lukas.bulwahn@gmail.com> Subject: [PATCH] MAINTAINERS: rectify two issues in KEYS-TRUSTED entry Date: Sun, 10 Feb 2019 18:59:16 +0000 [thread overview] Message-ID: <20190210185916.9915-1-lukas.bulwahn@gmail.com> (raw) In-Reply-To: <20190210185755.9776-1-lukas.bulwahn@gmail.com> Mimi Zohar used spaces instead of a tab when adding Jarkko Sakkinen as further maintainer to the KEYS-TRUSTED section entry. Paul McKenney also introduced a typo in Mimi Zohar's email address in the KEYS-TRUSTED section entry. The two issues were detected when writing a script that parses MAINTAINERS. Fixes: 34bccd61b139 ("MAINTAINERS: add Jarkko as maintainer for trusted keys") Fixes: 1dfddcdb95c4 ("MAINTAINERS: Update from @linux.vnet.ibm.com to @linux.ibm.com") Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com> --- Mimi, please pick up this patch instead of "[PATCH] MAINTAINERS: use tab instead of spaces". Thanks. MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index bf4965d6d5de..b4b62ea78eeb 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -8405,8 +8405,8 @@ 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: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> +M: Mimi Zohar <zohar@linux.ibm.com> L: linux-integrity@vger.kernel.org L: keyrings@vger.kernel.org S: Supported -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Lukas Bulwahn <lukas.bulwahn@gmail.com> To: James Bottomley <jejb@linux.ibm.com>, Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>, Mimi Zohar <zohar@linuxibm.com> Cc: paulmck@linux.vnet.ibm.com, linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org, Lukas Bulwahn <lukas.bulwahn@gmail.com> Subject: [PATCH] MAINTAINERS: rectify two issues in KEYS-TRUSTED entry Date: Sun, 10 Feb 2019 19:59:16 +0100 [thread overview] Message-ID: <20190210185916.9915-1-lukas.bulwahn@gmail.com> (raw) Mimi Zohar used spaces instead of a tab when adding Jarkko Sakkinen as further maintainer to the KEYS-TRUSTED section entry. Paul McKenney also introduced a typo in Mimi Zohar's email address in the KEYS-TRUSTED section entry. The two issues were detected when writing a script that parses MAINTAINERS. Fixes: 34bccd61b139 ("MAINTAINERS: add Jarkko as maintainer for trusted keys") Fixes: 1dfddcdb95c4 ("MAINTAINERS: Update from @linux.vnet.ibm.com to @linux.ibm.com") Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com> --- Mimi, please pick up this patch instead of "[PATCH] MAINTAINERS: use tab instead of spaces". Thanks. MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index bf4965d6d5de..b4b62ea78eeb 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -8405,8 +8405,8 @@ 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: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> +M: Mimi Zohar <zohar@linux.ibm.com> L: linux-integrity@vger.kernel.org L: keyrings@vger.kernel.org S: Supported -- 2.17.1
next prev parent reply other threads:[~2019-02-10 18:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-10 18:57 [PATCH] MAINTAINERS: rectify two issues in KEYS-TRUSTED entry Lukas Bulwahn 2019-02-10 18:57 ` Lukas Bulwahn 2019-02-10 18:59 ` Lukas Bulwahn [this message] 2019-02-10 18:59 ` Lukas Bulwahn 2019-02-10 19:00 ` Lukas Bulwahn 2019-02-10 19:00 ` Lukas Bulwahn 2019-02-10 20:32 ` Paul E. McKenney 2019-02-10 20:32 ` Paul E. McKenney 2019-02-11 14:09 ` Jarkko Sakkinen 2019-02-11 14:09 ` Jarkko Sakkinen
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=20190210185916.9915-1-lukas.bulwahn@gmail.com \ --to=lukas.bulwahn@gmail.com \ --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=paulmck@linux.vnet.ibm.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: linkBe 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.