From: Gerd Hoffmann <kraxel@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] hw/usb/bus.c: print device ID when 'info usb' used
Date: Fri, 28 Aug 2015 13:50:38 +0200 [thread overview]
Message-ID: <1440762638.20725.0.camel@redhat.com> (raw)
In-Reply-To: <57FA8C0D-64FF-4F71-8597-E36E0D1FF7E4@gmail.com>
On Mo, 2015-08-24 at 15:13 -0400, Programmingkid wrote:
> + monitor_printf(mon, " Device %d.%d, Port %s, Speed %s
> Mb/s,"
> + "Product %s, ID %s\n",
> + bus->busnr, dev->addr, port->path,
> + usb_speed(dev->speed),
> + dev->product_desc, dev->qdev.id);
>
dev->qdev.id can be NULL.
cheers,
Gerd
next prev parent reply other threads:[~2015-08-28 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 19:13 [Qemu-devel] [PATCH] hw/usb/bus.c: print device ID when 'info usb' used Programmingkid
2015-08-28 11:50 ` Gerd Hoffmann [this message]
2015-08-28 13:08 ` Programmingkid
2015-08-28 13:35 ` Daniel P. Berrange
2015-08-28 13:39 ` Programmingkid
2015-08-28 13:50 ` Daniel P. Berrange
2015-08-28 13:50 ` Gerd Hoffmann
2015-08-28 13:55 ` Programmingkid
2015-08-28 16:07 ` Peter Maydell
2015-08-28 16:09 ` Programmingkid
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=1440762638.20725.0.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=programmingkidx@gmail.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).