From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, marcandre.lureau@redhat.com
Subject: Re: [PATCH v3 0/3] tpm: Add missing ACPI device identification objects
Date: Sat, 27 Nov 2021 18:12:21 -0500 [thread overview]
Message-ID: <20211127181148-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f100e9ad-d55d-0d8b-83b2-3420beb5e892@linux.ibm.com>
On Fri, Nov 26, 2021 at 11:15:40PM -0500, Stefan Berger wrote:
> Is this series now acceptable for 'after 6.2'?
Sure. Tagged. Pls ping me aftre release to help make sure I don't lose
it.
>
> On 11/10/21 08:35, Stefan Berger wrote:
> > This series of patches adds missing ACPI device identification objects _STR
> > and _UID to TPM 1.2 and TPM 2 ACPI tables.
> >
> > Stefan
> >
> > v3:
> > - Dropped replacement of ACPI tables with empty files in 1/3.
> > - Reduced ignored files
> >
> > Stefan Berger (3):
> > tests: acpi: prepare for updated TPM related tables
> > acpi: tpm: Add missing device identification objects
> > tests: acpi: Add updated TPM related tables
> >
> > hw/arm/virt-acpi-build.c | 1 +
> > hw/i386/acpi-build.c | 8 ++++++++
> > tests/data/acpi/q35/DSDT.tis.tpm12 | Bin 8894 -> 8900 bytes
> > tests/data/acpi/q35/DSDT.tis.tpm2 | Bin 8894 -> 8921 bytes
> > 4 files changed, 9 insertions(+)
> >
prev parent reply other threads:[~2021-11-27 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 13:35 [PATCH v3 0/3] tpm: Add missing ACPI device identification objects Stefan Berger
2021-11-10 13:35 ` [PATCH v3 1/3] tests: acpi: prepare for updated TPM related tables Stefan Berger
2021-11-10 13:35 ` [PATCH v3 2/3] acpi: tpm: Add missing device identification objects Stefan Berger
2021-11-10 13:35 ` [PATCH v3 3/3] tests: acpi: Add updated TPM related tables Stefan Berger
2021-11-27 4:15 ` [PATCH v3 0/3] tpm: Add missing ACPI device identification objects Stefan Berger
2021-11-27 23:12 ` Michael S. Tsirkin [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=20211127181148-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--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;
as well as URLs for NNTP newsgroup(s).