From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Matthew Garrett <mjg59@google.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-integrity <linux-integrity@vger.kernel.org>,
linux-doc@vger.kernel.org, "Thiébaud Weksteen" <tweek@google.com>,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH] tpm: Document UEFI event log quirks
Date: Fri, 12 Jul 2019 15:41:17 +0300 [thread overview]
Message-ID: <20190712124117.itno74ucilqvoseo@linux.intel.com> (raw)
In-Reply-To: <CACdnJuu0gFySbcMY7Fpps-j8KP+rCifznOeo18P47UBQAygPVQ@mail.gmail.com>
On Mon, Jul 08, 2019 at 01:43:14PM -0700, Matthew Garrett wrote:
> On Wed, Jul 3, 2019 at 9:11 AM Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> > +Before calling ExitBootServices() Linux EFI stub copies the event log to
> > +a custom configuration table defined by the stub itself. Unfortanely,
> > +the events generated by ExitBootServices() do end up to the table.
>
> "Unfortunately, the events generated by ExitBootServices() occur after
> this and don't end up in the table"?
Oops, it is a typo, thanks :-)
/Jarkko
prev parent reply other threads:[~2019-07-12 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 16:11 [PATCH] tpm: Document UEFI event log quirks Jarkko Sakkinen
2019-07-03 16:45 ` Randy Dunlap
2019-07-05 10:15 ` Jarkko Sakkinen
2019-07-07 19:33 ` Randy Dunlap
2019-07-08 15:25 ` Jarkko Sakkinen
2019-07-03 17:08 ` Jordan Hand
2019-07-05 10:26 ` Jarkko Sakkinen
2019-07-08 4:10 ` Jordan Hand
2019-07-08 15:27 ` Jarkko Sakkinen
2019-07-05 10:11 ` Jarkko Sakkinen
2019-07-08 20:43 ` Matthew Garrett
2019-07-12 12:41 ` Jarkko Sakkinen [this message]
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=20190712124117.itno74ucilqvoseo@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@google.com \
--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 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.