From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Eddie James <eajames@linux.ibm.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
jgg@ziepe.ca, peterhuewe@gmx.de
Subject: Re: [PATCH v2 2/2] tpm: Add reserved memory event log
Date: Sat, 21 Jan 2023 03:58:33 +0000 [thread overview]
Message-ID: <Y8ti6RVfLAf2+tau@kernel.org> (raw)
In-Reply-To: <adced60c-3abe-8f14-9146-e15cee98d5ee@linux.ibm.com>
On Wed, Jan 18, 2023 at 10:01:16AM -0500, Stefan Berger wrote:
>
>
> On 1/18/23 09:49, Eddie James wrote:
> >
> > On 1/18/23 07:27, Stefan Berger wrote:
> > >
> > >
> > > On 1/13/23 11:10, Eddie James wrote:
> > > > Some platforms may desire to pass the event log up to linux in the
> > >
> > > Which platforms are these that work like this?
> >
> >
> > Platforms booting from U-Boot without EFI. So at the moment, IBM's OpenBMC systems hope to use this.
>
> It may be worth to mention this in the patch description in case someone wonders which
> systems would take that path.
+1
BR, Jarkko
next prev parent reply other threads:[~2023-01-21 3:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 16:10 [PATCH v2 0/2] tpm: Add reserved memory event log Eddie James
2023-01-13 16:10 ` [PATCH v2 1/2] tpm: Use managed allocation for bios " Eddie James
2023-01-21 0:11 ` Jarkko Sakkinen
2023-01-25 19:06 ` Eddie James
2023-01-26 17:31 ` Jarkko Sakkinen
2023-01-13 16:10 ` [PATCH v2 2/2] tpm: Add reserved memory " Eddie James
2023-01-18 13:27 ` Stefan Berger
2023-01-18 14:49 ` Eddie James
2023-01-18 15:01 ` Stefan Berger
2023-01-21 3:58 ` Jarkko Sakkinen [this message]
2023-01-21 0:13 ` 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=Y8ti6RVfLAf2+tau@kernel.org \
--to=jarkko@kernel.org \
--cc=eajames@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stefanb@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