From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 2/3] tpm: Rearrange ACPI log code to easier extend for TPM2 case
Date: Tue, 31 Mar 2020 14:51:57 +0300 [thread overview]
Message-ID: <20200331115157.GB8295@linux.intel.com> (raw)
In-Reply-To: <2474521e-909c-d8b4-077b-2043ce587130@linux.ibm.com>
On Mon, Mar 30, 2020 at 05:12:24PM -0400, Stefan Berger wrote:
> On 3/30/20 3:32 PM, Jarkko Sakkinen wrote:
> > On Mon, Mar 30, 2020 at 11:15:35AM -0400, Stefan Berger wrote:
> > > From: Stefan Berger <stefanb@linux.ibm.com>
> > >
> > > Rearrange the ACPI table based log code to allow for easier extension
> > > for the TPM2 case.
> > >
> > > Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> > I think this change does not do anything useful.
>
> I know. So it's easy to see what's happening and harmless. But I'll squash
> it.
Yeah, well files aren't getting moved or anything and overally
the change is still somewhat scoped.
/Jarkko
next prev parent reply other threads:[~2020-03-31 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 15:15 [PATCH v2 0/3] tpm2: Make TPM2 logs accessible for non-UEFI firmware Stefan Berger
2020-03-30 15:15 ` [PATCH v2 1/3] acpi: Extend TPM2 ACPI table with missing log fields Stefan Berger
2020-03-30 19:28 ` Jarkko Sakkinen
2020-03-30 21:26 ` Stefan Berger
2020-03-31 11:55 ` Jarkko Sakkinen
2020-03-30 15:15 ` [PATCH v2 2/3] tpm: Rearrange ACPI log code to easier extend for TPM2 case Stefan Berger
2020-03-30 19:32 ` Jarkko Sakkinen
2020-03-30 21:12 ` Stefan Berger
2020-03-31 11:51 ` Jarkko Sakkinen [this message]
2020-03-30 15:15 ` [PATCH v2 3/3] tpm: Add support for ACPI logs from TPM2 ACPI table Stefan Berger
2020-03-30 19:54 ` 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=20200331115157.GB8295@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
--cc=stefanb@linux.vnet.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 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.