qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v1 0/1] Merge tpm 2020/01/29 v1
Date: Thu, 30 Jan 2020 14:18:32 +0000	[thread overview]
Message-ID: <CAFEAcA89n7bsdvG9kpxUhu35DvpYrtv4ngrMwtDM8UeKw8zApw@mail.gmail.com> (raw)
In-Reply-To: <20200129130845.1886915-1-stefanb@linux.vnet.ibm.com>

On Wed, 29 Jan 2020 at 13:09, Stefan Berger <stefanb@linux.vnet.ibm.com> wrote:
>
> This patch fixes a post-copy migration error due to an unaligned start address.
>
>    Stefan
>
> The following changes since commit 4c60e3289875ae6c516a37523bcecb87f68ce67c:
>
>   Merge remote-tracking branch 'remotes/rth/tags/pull-pa-20200127' into staging (2020-01-28 15:11:04 +0000)
>
> are available in the Git repository at:
>
>   git://github.com/stefanberger/qemu-tpm.git tags/pull-tpm-2020-01-29-1
>
> for you to fetch changes up to 71e415c8a75c130875f14d6b2136825789feb297:
>
>   tpm-ppi: page-align PPI RAM (2020-01-29 07:27:07 -0500)
>
> ----------------------------------------------------------------
> Merge tpm 2020/01/29 v1
>
> ----------------------------------------------------------------
> Marc-André Lureau (1):
>       tpm-ppi: page-align PPI RAM
>
>  hw/tpm/tpm_ppi.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/5.0
for any user-visible changes.

-- PMM


      parent reply	other threads:[~2020-01-30 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 13:08 [PULL v1 0/1] Merge tpm 2020/01/29 v1 Stefan Berger
2020-01-29 13:08 ` [PULL v1 1/1] tpm-ppi: page-align PPI RAM Stefan Berger
2020-01-30 14:18 ` 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=CAFEAcA89n7bsdvG9kpxUhu35DvpYrtv4ngrMwtDM8UeKw8zApw@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).