[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190731133948.1a527db8@lwn.net>
Date: Wed, 31 Jul 2019 13:39:48 -0600
From: Jonathan Corbet <corbet@....net>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-doc@...r.kernel.org, tweek@...gle.com,
matthewgarrett@...gle.com, jorhand@...ux.microsoft.com,
rdunlap@...radead.org, Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH v4] tpm: Document UEFI event log quirks
On Fri, 12 Jul 2019 18:44:32 +0300
Jarkko Sakkinen <jarkko.sakkinen@...ux.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@...ux.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
Powered by blists - more mailing lists