From: Richard Henderson <richard.henderson@linaro.org>
To: Stefan Berger <stefanb@linux.ibm.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [PULL v1 0/2] Merge tpm 2022/06/07 v1
Date: Wed, 8 Jun 2022 07:40:48 -0700 [thread overview]
Message-ID: <0fc46d21-9eba-51d3-1d94-fed7dc5aff24@linaro.org> (raw)
In-Reply-To: <20220608010006.2122022-1-stefanb@linux.ibm.com>
On 6/7/22 18:00, Stefan Berger wrote:
> Hi!
>
> The patches in this PR resolve several Coverity issues and mark a memory
> region with TPM response data as dirty so that it does not get lost during
> migration.
>
> Stefan
Applied, thanks. Please update https://wiki.qemu.org/ChangeLog/7.1 as appropriate.
r~
>
> The following changes since commit 7077fcb9b68f058809c9dd9fd1dacae1881e886c:
>
> Merge tag 'vmbus-maint-20220530' of https://github.com/maciejsszmigiero/qemu into staging (2022-05-30 12:40:36 -0700)
>
> are available in the Git repository at:
>
> https://github.com/stefanberger/qemu-tpm.git tags/pull-tpm-2022-06-07-1
>
> for you to fetch changes up to e37a0ef4605e5d2041785ff3fc89ca6021faf7a0:
>
> tpm_crb: mark command buffer as dirty on request completion (2022-06-07 20:37:25 -0400)
>
> Anthony PERARD (1):
> tpm_crb: mark command buffer as dirty on request completion
>
> Peter Maydell (1):
> hw/tpm/tpm_tis_common.c: Assert that locty is in range
>
> hw/tpm/tpm_crb.c | 1 +
> hw/tpm/tpm_tis_common.c | 7 ++++++-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2022-06-08 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 1:00 [PULL v1 0/2] Merge tpm 2022/06/07 v1 Stefan Berger
2022-06-08 1:00 ` [PULL v1 1/2] hw/tpm/tpm_tis_common.c: Assert that locty is in range Stefan Berger
2022-06-08 1:00 ` [PULL v1 2/2] tpm_crb: mark command buffer as dirty on request completion Stefan Berger
2022-06-08 14:40 ` Richard Henderson [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=0fc46d21-9eba-51d3-1d94-fed7dc5aff24@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--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).