From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: James Bottomley <jejb@linux.ibm.com>,
Mimi Zohar <zohar@linuxibm.com>,
paulmck@linux.vnet.ibm.com, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: rectify two issues in KEYS-TRUSTED entry
Date: Mon, 11 Feb 2019 14:09:55 +0000 [thread overview]
Message-ID: <20190211140955.GC8431@linux.intel.com> (raw)
In-Reply-To: <20190210185755.9776-1-lukas.bulwahn@gmail.com>
On Sun, Feb 10, 2019 at 07:57:55PM +0100, Lukas Bulwahn wrote:
> 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>
Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: James Bottomley <jejb@linux.ibm.com>,
Mimi Zohar <zohar@linuxibm.com>,
paulmck@linux.vnet.ibm.com, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: rectify two issues in KEYS-TRUSTED entry
Date: Mon, 11 Feb 2019 16:09:55 +0200 [thread overview]
Message-ID: <20190211140955.GC8431@linux.intel.com> (raw)
In-Reply-To: <20190210185755.9776-1-lukas.bulwahn@gmail.com>
On Sun, Feb 10, 2019 at 07:57:55PM +0100, Lukas Bulwahn wrote:
> 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>
Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
/Jarkko
next prev parent reply other threads:[~2019-02-11 14:09 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
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 [this message]
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=20190211140955.GC8431@linux.intel.com \
--to=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=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: 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.