From: Gerd Hoffmann <kraxel@redhat.com>
To: Juergen Gross <jgross@suse.com>
Cc: qemu-devel@nongnu.org, xen-devel@lists.xensource.com,
sstabellini@kernel.org, anthony.perard@citrix.com
Subject: Re: [Qemu-devel] [PATCH] xen: use a common function for pv and hvm guest backend register calls
Date: Tue, 02 Aug 2016 13:40:56 +0200 [thread overview]
Message-ID: <1470138056.30562.95.camel@redhat.com> (raw)
In-Reply-To: <1470119552-16170-1-git-send-email-jgross@suse.com>
On Di, 2016-08-02 at 08:32 +0200, Juergen Gross wrote:
> Instead of calling xen_be_register() for each supported backend type
> for hvm and pv guests in their machine init functions use a common
> function in order not to have to add new backends twice.
>
> This at once fixes the error that hvm domains couldn't use the qusb
> backend.
Looks good to me. Should I take this through the usb patch queue,
together with the other xen-usb fixes (once codestyle issues are fixed)?
If so, can I get an ack from xen please, preferably fast enough for
-rc2?
thanks,
Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Juergen Gross <jgross@suse.com>
Cc: anthony.perard@citrix.com, xen-devel@lists.xensource.com,
sstabellini@kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] xen: use a common function for pv and hvm guest backend register calls
Date: Tue, 02 Aug 2016 13:40:56 +0200 [thread overview]
Message-ID: <1470138056.30562.95.camel@redhat.com> (raw)
In-Reply-To: <1470119552-16170-1-git-send-email-jgross@suse.com>
On Di, 2016-08-02 at 08:32 +0200, Juergen Gross wrote:
> Instead of calling xen_be_register() for each supported backend type
> for hvm and pv guests in their machine init functions use a common
> function in order not to have to add new backends twice.
>
> This at once fixes the error that hvm domains couldn't use the qusb
> backend.
Looks good to me. Should I take this through the usb patch queue,
together with the other xen-usb fixes (once codestyle issues are fixed)?
If so, can I get an ack from xen please, preferably fast enough for
-rc2?
thanks,
Gerd
next prev parent reply other threads:[~2016-08-02 11:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 6:32 [Qemu-devel] [PATCH] xen: use a common function for pv and hvm guest backend register calls Juergen Gross
2016-08-02 6:32 ` Juergen Gross
2016-08-02 11:40 ` Gerd Hoffmann [this message]
2016-08-02 11:40 ` Gerd Hoffmann
2016-08-02 18:32 ` [Qemu-devel] " Stefano Stabellini
2016-08-02 18:32 ` Stefano Stabellini
2016-08-02 17:43 ` [Qemu-devel] " Anthony PERARD
2016-08-02 17:43 ` Anthony PERARD
2016-08-02 18:27 ` [Qemu-devel] " Stefano Stabellini
2016-08-02 18:27 ` Stefano Stabellini
2016-08-03 3:56 ` [Qemu-devel] " Juergen Gross
2016-08-03 3:56 ` Juergen Gross
2016-08-03 17:50 ` [Qemu-devel] " Stefano Stabellini
2016-08-03 17:50 ` Stefano Stabellini
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=1470138056.30562.95.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=jgross@suse.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.