From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 0/3] Merge tpm 2018/12/04 v1
Date: Thu, 13 Dec 2018 11:33:21 +0000 [thread overview]
Message-ID: <CAFEAcA-Ao54gvA631bcOrMAK2s0x+PtpE6M5MQ1AFpAz-g8PdA@mail.gmail.com> (raw)
In-Reply-To: <20181211205654.3550341-1-stefanb@linux.vnet.ibm.com>
On Tue, 11 Dec 2018 at 20:57, Stefan Berger <stefanb@linux.vnet.ibm.com> wrote:
>
> This series of patches removes an unnecessary parameter from tpm_tis_abort()
> and adds a locality range check (using assert()) to tpm_tis_prep_abort() and
> tpm_tis_request_completed().
>
> Stefan
>
> The following changes since commit 83ea23cd207a03c5736be0231acbf7f8b05dbf52:
>
> i386: hvf: Fix overrun of _decode_tbl1 (2018-12-03 15:09:55 +0000)
>
> are available in the Git repository at:
>
> git://github.com/stefanberger/qemu-tpm.git tags/pull-tpm-2018-12-04-1
>
> for you to fetch changes up to a639f96111eadb3b8e3021fd3f27e2948ad1c640:
>
> tpm: Make sure the locality received from backend is valid (2018-12-04 10:21:25 -0500)
>
> ----------------------------------------------------------------
> Stefan Berger (3):
> tpm: Remove unused locty parameter from tpm_tis_abort()
> tpm: Make sure new locality passed to tpm_tis_prep_abort() is valid
> tpm: Make sure the locality received from backend is valid
>
Applied, thanks.
-- PMM
prev parent reply other threads:[~2018-12-13 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 20:56 [Qemu-devel] [PULL v2 0/3] Merge tpm 2018/12/04 v1 Stefan Berger
2018-12-11 20:56 ` [Qemu-devel] [PULL v2 1/3] tpm: Remove unused locty parameter from tpm_tis_abort() Stefan Berger
2018-12-11 20:56 ` [Qemu-devel] [PULL v2 2/3] tpm: Make sure new locality passed to tpm_tis_prep_abort() is valid Stefan Berger
2018-12-11 20:56 ` [Qemu-devel] [PULL v2 3/3] tpm: Make sure the locality received from backend " Stefan Berger
2018-12-13 11:33 ` Peter Maydell [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=CAFEAcA-Ao54gvA631bcOrMAK2s0x+PtpE6M5MQ1AFpAz-g8PdA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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 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).