From: Gerd Hoffmann <kraxel@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] usb: Resolve warnings about unassigned bus on usb device creation
Date: Mon, 27 Feb 2012 15:03:18 +0100 [thread overview]
Message-ID: <4F4B8D26.3070400@redhat.com> (raw)
In-Reply-To: <4F4B8BE2.8090309@siemens.com>
On 02/27/12 14:57, Jan Kiszka wrote:
> On 2012-02-02 18:59, Jan Kiszka wrote:
>> When creating an USB device the old way, there is no way to specify the
>> target bus. Thus the warning issued by usb_create makes no sense and
>> rather confuses our users.
>>
>> Resolve this by passing a bus reference to the usbdevice_init handler
>> and letting those handlers forward it to usb_create.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
> Ping.
>
Somehow slipped through. Looks good, but needs a rebase.
cheers,
Gerd
prev parent reply other threads:[~2012-02-27 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 17:59 [Qemu-devel] [PATCH] usb: Resolve warnings about unassigned bus on usb device creation Jan Kiszka
2012-02-03 21:15 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2012-02-27 13:57 ` [Qemu-devel] [PATCH] " Jan Kiszka
2012-02-27 14:03 ` Gerd Hoffmann [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=4F4B8D26.3070400@redhat.com \
--to=kraxel@redhat.com \
--cc=jan.kiszka@siemens.com \
--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).