qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PULL 0/5] virtio, vhost, pc: fixes
Date: Thu, 1 Dec 2016 13:39:03 +0000	[thread overview]
Message-ID: <20161201133903.GI10441@stefanha-x1.localdomain> (raw)
In-Reply-To: <1480564455-23933-1-git-send-email-mst@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]

On Thu, Dec 01, 2016 at 05:58:40AM +0200, Michael S. Tsirkin wrote:
> Comments on patches included:
> 
> - a spec update seems important for 2.8 as incorrect
> spec makes people implement backends incorrectly.
> - undefined behaviour fix seems important too -
> who knows what would compiler optimizers come up with
> 
> Others are imho clearly uncontroversial.
> 
> 
> The following changes since commit 1cd56fd2e14f67ead2f0458b4ae052f19865c41c:
> 
>   Update version for v2.8.0-rc2 release (2016-11-29 22:26:25 +0000)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
> 
> for you to fetch changes up to 9730280d54634caa5d63f0d8fcd85da8311d2ebf:
> 
>   virtio-crypto: fix uninitialized variables (2016-11-30 04:22:18 +0200)
> 
> ----------------------------------------------------------------
> virtio, vhost, pc: fixes
> 
> Minor fixes since 2.8.0-rc2.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> 
> ----------------------------------------------------------------
> Gonglei (1):
>       virtio-crypto: fix uninitialized variables
> 
> Laszlo Ersek (2):
>       loader: fix handling of custom address spaces when adding ROM blobs
>       loader: fix undefined behavior in rom_order_compare()
> 
> Peter Xu (1):
>       intel_iommu: fix incorrect device invalidate
> 
> Wei Wang (1):
>       spec/vhost-user: fix the VHOST_USER prefix
> 
>  docs/specs/vhost-user.txt | 20 ++++++++++----------
>  hw/lm32/lm32_hwsetup.h    |  2 +-
>  include/hw/loader.h       |  6 +++---
>  hw/arm/virt-acpi-build.c  |  2 +-
>  hw/core/loader.c          |  6 ++++--
>  hw/i386/acpi-build.c      |  2 +-
>  hw/i386/intel_iommu.c     |  1 +
>  hw/virtio/virtio-crypto.c |  2 +-
>  8 files changed, 22 insertions(+), 19 deletions(-)
> 

Thanks, applied to my staging tree:
https://github.com/stefanha/qemu/commits/staging

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      parent reply	other threads:[~2016-12-01 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  3:58 [Qemu-devel] [PULL 0/5] virtio, vhost, pc: fixes Michael S. Tsirkin
2016-12-01  3:58 ` [Qemu-devel] [PULL 1/5] spec/vhost-user: fix the VHOST_USER prefix Michael S. Tsirkin
2016-12-01  3:58 ` [Qemu-devel] [PULL 2/5] intel_iommu: fix incorrect device invalidate Michael S. Tsirkin
2016-12-01  3:58 ` [Qemu-devel] [PULL 3/5] loader: fix handling of custom address spaces when adding ROM blobs Michael S. Tsirkin
2016-12-01  3:58 ` [Qemu-devel] [PULL 4/5] loader: fix undefined behavior in rom_order_compare() Michael S. Tsirkin
2016-12-01  3:58 ` [Qemu-devel] [PULL 5/5] virtio-crypto: fix uninitialized variables Michael S. Tsirkin
2016-12-01 13:39 ` Stefan Hajnoczi [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=20161201133903.GI10441@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).