From: Jonathan Corbet <corbet@lwn.net>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-doc@vger.kernel.org, tweek@google.com,
matthewgarrett@google.com, jorhand@linux.microsoft.com,
rdunlap@infradead.org, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v4] tpm: Document UEFI event log quirks
Date: Wed, 31 Jul 2019 13:39:48 -0600 [thread overview]
Message-ID: <20190731133948.1a527db8@lwn.net> (raw)
In-Reply-To: <20190712154439.10642-1-jarkko.sakkinen@linux.intel.com>
On Fri, 12 Jul 2019 18:44:32 +0300
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
> There are some weird quirks when it comes to UEFI event log. Provide a
> brief introduction to TPM event log mechanism and describe the quirks
> and how they can be sorted out.
>
> Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> ---
> v4: - Unfortanely -> Unfortunately
> v3: - Add a section for refs and use a bullet list to enumerate them.
> - Remove an invalid author info.
> v2: - Fix one typo.
> - Refine the last paragraph to better explain how the two halves
> of the event log are concatenated.
> Documentation/security/tpm/index.rst | 1 +
> Documentation/security/tpm/tpm_event_log.rst | 55 ++++++++++++++++++++
> 2 files changed, 56 insertions(+)
> create mode 100644 Documentation/security/tpm/tpm_event_log.rst
I've applied this, thanks. Before I could do so, though, I had to edit
the headers, which read:
> Content-Type: text/plain; charset=y
"git am" *really* doesn't like "charset=y". I think this is something
that git send-email likes to do occasionally, don't know why...
Thanks,
jon
next prev parent reply other threads:[~2019-07-31 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 15:44 [PATCH v4] tpm: Document UEFI event log quirks Jarkko Sakkinen
2019-07-31 19:39 ` Jonathan Corbet [this message]
2019-08-01 17:43 ` 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=20190731133948.1a527db8@lwn.net \
--to=corbet@lwn.net \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jorhand@linux.microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=tweek@google.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