From: prsriva <prsriva@linux.microsoft.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
Thiago Jung Bauermann <bauerman@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-integrity@vger.kernel.org, jmorris@namei.org
Subject: Re: [RFC][PATCH 1/1] Carry ima measurement log for arm64 via kexec_file_load
Date: Mon, 9 Sep 2019 16:18:59 -0700 [thread overview]
Message-ID: <cb7840de-b26b-7e56-9d9a-dac5ccd8692f@linux.microsoft.com> (raw)
In-Reply-To: <1567985476.4614.224.camel@linux.ibm.com>
On 9/8/19 4:31 PM, Mimi Zohar wrote:
> Hi Prakhar,
> "Carrying over the ima log during kexec_file_load" was originally
> posted on 5/10 and 5/31 without a cover letter. On 8/29 it was
> reposted as an RFC with a cover letter. The cover letter was v1, but
> the patch itself was not. In the future, please use the "git format-
> patch "-subject-prefix" option to add the version number to both the
> cover letter and the patches.
>
> The comments you received were based on the 8/29 version. I haven't
> seen anything after that.
>
> Mimi
Added the correct subject prefix, resent patches.
I resent the patches sent at 5/31, since i had no response.
v1 version addresses the comments in the RFC patch.
I have cc-ed you to the email, hopefully its not missed again.
Thankyou for pointing it out.
Thanks,
Prakhar Srivastava
next prev parent reply other threads:[~2019-09-09 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 20:05 [RFC][PATCH v1 0/1] Carry ima measurement log for arm64 via kexec_file_load Prakhar Srivastava
2019-08-29 20:05 ` [RFC][PATCH 1/1] " Prakhar Srivastava
2019-08-30 5:23 ` Stephen Boyd
2019-08-31 0:17 ` Thiago Jung Bauermann
2019-08-31 0:11 ` Thiago Jung Bauermann
2019-09-06 23:56 ` prsriva
2019-09-08 23:31 ` Mimi Zohar
2019-09-09 23:18 ` prsriva [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-29 19:00 [RFC][PATCH v1 0/1] " Prakhar Srivastava
2019-08-29 19:00 ` [RFC][PATCH 1/1] " Prakhar Srivastava
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=cb7840de-b26b-7e56-9d9a-dac5ccd8692f@linux.microsoft.com \
--to=prsriva@linux.microsoft.com \
--cc=bauerman@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-arm-msm@vger.kernel.org \
--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).