qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: stefanha@redhat.com, peter.maydell@linaro.org,
	anthony.perard@citrix.com, xen-devel@lists.xenproject.org,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/5] xen-20161122-tag
Date: Tue, 22 Nov 2016 19:31:08 +0000	[thread overview]
Message-ID: <20161122193108.GD16392@stefanha-x1.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.10.1611221037010.21858@sstabellini-ThinkPad-X260>

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

On Tue, Nov 22, 2016 at 10:45:58AM -0800, Stefano Stabellini wrote:
> Hi Stefan,
> 
> this pull request contains an XSA ("fix ioreq handling") and xen-usb bug
> fixes and cleanups. Please note that "qdev: add function qdev_set_id()"
> touches generic qdev code: I was the only one to review the patch but it
> is just code movement.
> 
> 
> The following changes since commit a7764f1548ef9946af30a8f96be9cef10761f0c1:
> 
>   Fix FreeBSD (10.x) build after 7dc9ae43 (2016-11-22 10:56:01 +0000)
> 
> are available in the git repository at:
> 
>   git://xenbits.xen.org/people/sstabellini/qemu-dm.git tags/xen-20161122-tag
> 
> for you to fetch changes up to f1784a222eed213ce3213f431bc2f9c570f20c3e:
> 
>   xen: attach pvusb usb bus to backend qdev (2016-11-22 10:29:41 -0800)
> 
> ----------------------------------------------------------------
> Xen 2016/11/22
> 
> ----------------------------------------------------------------
> Jan Beulich (1):
>       xen: fix ioreq handling
> 
> Juergen Gross (4):
>       xen: add an own bus for xen backend devices
>       qdev: add function qdev_set_id()
>       xen: create qdev for each backend device
>       xen: attach pvusb usb bus to backend qdev
> 
>  hw/usb/xen-usb.c             | 23 +++++++--------
>  hw/xen/xen_backend.c         | 66 ++++++++++++++++++++++++++++++++++++++++++--
>  hw/xen/xen_pvdev.c           |  4 ++-
>  include/hw/xen/xen_backend.h |  8 ++++++
>  include/hw/xen/xen_pvdev.h   |  1 +
>  include/monitor/qdev.h       |  1 +
>  qdev-monitor.c               | 36 +++++++++++++-----------
>  xen-hvm.c                    | 16 ++++++++++-
>  8 files changed, 121 insertions(+), 34 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-11-22 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 18:45 [Qemu-devel] [PULL 0/5] xen-20161122-tag Stefano Stabellini
2016-11-22 18:46 ` [Qemu-devel] [PULL 1/5] xen: fix ioreq handling Stefano Stabellini
2016-11-22 18:46   ` [Qemu-devel] [PULL 2/5] xen: add an own bus for xen backend devices Stefano Stabellini
2016-11-22 18:46   ` [Qemu-devel] [PULL 3/5] qdev: add function qdev_set_id() Stefano Stabellini
2016-11-22 18:46   ` [Qemu-devel] [PULL 4/5] xen: create qdev for each backend device Stefano Stabellini
2016-11-22 18:46   ` [Qemu-devel] [PULL 5/5] xen: attach pvusb usb bus to backend qdev Stefano Stabellini
2016-11-22 19:31 ` 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=20161122193108.GD16392@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=anthony.perard@citrix.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=stefanha@redhat.com \
    --cc=xen-devel@lists.xenproject.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).