From: Avi Kivity <avi@redhat.com>
To: Veruca Salt <verucasaltuk@hotmail.co.uk>
Cc: QEMU-KVM Mailing List <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [ANNOUNCE] qemu-kvm-1.1-rc3
Date: Mon, 28 May 2012 12:30:58 +0300 [thread overview]
Message-ID: <4FC345D2.3090309@redhat.com> (raw)
In-Reply-To: <SNT112-W60E3D67974E624C301F7B590010@phx.gbl>
On 05/25/2012 11:36 AM, Veruca Salt wrote:
>
> Avi- would love to test out 1.1, as we are currently using the ehci method
> which has been frozen at 'experimental' for so long.
>
> Is there any user documentation on the xhci methods?
Copying qemu-devel, where someone may know the answer.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Veruca Salt <verucasaltuk@hotmail.co.uk>
Cc: qemu-devel <qemu-devel@nongnu.org>,
QEMU-KVM Mailing List <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [ANNOUNCE] qemu-kvm-1.1-rc3
Date: Mon, 28 May 2012 12:30:58 +0300 [thread overview]
Message-ID: <4FC345D2.3090309@redhat.com> (raw)
In-Reply-To: <SNT112-W60E3D67974E624C301F7B590010@phx.gbl>
On 05/25/2012 11:36 AM, Veruca Salt wrote:
>
> Avi- would love to test out 1.1, as we are currently using the ehci method
> which has been frozen at 'experimental' for so long.
>
> Is there any user documentation on the xhci methods?
Copying qemu-devel, where someone may know the answer.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-28 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 9:07 [ANNOUNCE] qemu-kvm-1.1-rc3 Avi Kivity
2012-05-25 8:36 ` Veruca Salt
2012-05-28 9:30 ` Avi Kivity [this message]
2012-05-28 9:30 ` [Qemu-devel] " Avi Kivity
2012-05-29 8:32 ` qemu & xhci mini howto (was: Re: [Qemu-devel] [ANNOUNCE] qemu-kvm-1.1-rc3) Gerd Hoffmann
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=4FC345D2.3090309@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=verucasaltuk@hotmail.co.uk \
/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.