From: Denis Efremov <efremov@linux.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
joe@perches.com, linux-kernel@vger.kernel.org,
Denis Kenzior <denkenz@gmail.com>,
James Bottomley <jejb@linux.ibm.com>,
Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org
Subject: Re: [RESEND PATCH] MAINTAINERS: keys: Update path to trusted.h
Date: Tue, 10 Sep 2019 14:50:39 +0300 [thread overview]
Message-ID: <b1a3742e-4d35-ebf6-2127-bc857c09997d@linux.com> (raw)
In-Reply-To: <20190816185823.kjuxqfegpsywulkn@linux.intel.com>
Hi,
On 8/16/19 9:58 PM, Jarkko Sakkinen wrote:
> On Fri, Aug 16, 2019 at 01:12:00AM +0300, Denis Efremov wrote:
>> Update MAINTAINERS record to reflect that trusted.h
>> was moved to a different directory in commit 22447981fc05
>> ("KEYS: Move trusted.h to include/keys [ver #2]").
>>
>> Cc: Denis Kenzior <denkenz@gmail.com>
>> Cc: James Bottomley <jejb@linux.ibm.com>
>> Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>> Cc: Mimi Zohar <zohar@linux.ibm.com>
>> Cc: linux-integrity@vger.kernel.org
>> Signed-off-by: Denis Efremov <efremov@linux.com>
>
> Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
> /Jarkko
>
Could someone take this fix through his tree?
Thanks,
Denis
next prev parent reply other threads:[~2019-09-10 11:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-03-25 21:27 ` Bad file pattern in MAINTAINERS section 'KEYS-TRUSTED' Joe Perches
2019-03-26 11:37 ` Jarkko Sakkinen
2019-03-26 12:10 ` Mimi Zohar
2019-03-26 14:25 ` James Bottomley
2019-03-26 14:59 ` Denis Kenzior
2019-03-26 16:25 ` James Bottomley
2019-03-27 4:58 ` Jarkko Sakkinen
2019-03-27 4:54 ` Jarkko Sakkinen
2019-08-13 6:57 ` Denis Efremov
2019-08-15 21:57 ` Jarkko Sakkinen
2019-08-15 22:12 ` [RESEND PATCH] MAINTAINERS: keys: Update path to trusted.h Denis Efremov
2019-08-16 18:58 ` Jarkko Sakkinen
2019-09-10 11:50 ` Denis Efremov [this message]
2019-09-14 13:50 ` 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=b1a3742e-4d35-ebf6-2127-bc857c09997d@linux.com \
--to=efremov@linux.com \
--cc=denkenz@gmail.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=joe@perches.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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 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).