From: Brad Hards <bradh@frogmouth.net>
To: qemu-devel@nongnu.org
Cc: Hans de Goede <hdegoede@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] usb: use DPRINTF instead of printf for some simple cases
Date: Mon, 25 Apr 2011 11:02:17 +1000 [thread overview]
Message-ID: <201104251102.17145.bradh@frogmouth.net> (raw)
In-Reply-To: <201104140801.43238.bradh@frogmouth.net>
On Thursday 14 April 2011 08:01:43 Brad Hards wrote:
> On Wed, 13 Apr 2011 10:52:37 pm Hans de Goede wrote:
> > > @@ -359,7 +359,7 @@ static int usb_host_claim_interfaces(USBHostDevice
> > > *dev, int configuration)
> > >
> > > ret = ioctl(dev->fd, USBDEVFS_CLAIMINTERFACE,&interface);
> > > if (ret< 0) {
> > >
> > > if (errno == EBUSY) {
> > >
> > > - printf("husb: update iface. device already
> > > grabbed\n"); + DPRINTF("husb: update iface. device
> > > already grabbed\n");
> > >
> > > } else {
> > >
> > > perror("husb: failed to claim interface");
> > >
> > > }
> >
> > Nack, this is an error condition, so it should not be a DPRINTF.
>
> Then should it go to stderr instead of stdout?
>
> (There are other places in this code where we use fprintf(stderr, ...) to
> indicate error conditions.)
ping?
Brad
next prev parent reply other threads:[~2011-04-25 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 9:45 [Qemu-devel] [PATCH 0/4] Minor USB fixes Brad Hards
2011-04-13 9:45 ` [Qemu-devel] [PATCH 1/4] usb: trivial spelling fixes Brad Hards
2011-04-13 9:45 ` [Qemu-devel] [PATCH 2/4] usb: initialise data element in Linux USB_DISCONNECT ioctl Brad Hards
2011-04-13 9:45 ` [Qemu-devel] [PATCH 3/4] usb: fix spelling errors in usb-linux.c Brad Hards
2011-04-13 9:45 ` [Qemu-devel] [PATCH 4/4] usb: use DPRINTF instead of printf for some simple cases Brad Hards
2011-04-13 12:36 ` Stefan Hajnoczi
2011-04-13 12:52 ` Hans de Goede
2011-04-13 22:01 ` Brad Hards
2011-04-25 1:02 ` Brad Hards [this message]
2011-04-13 12:37 ` [Qemu-devel] [PATCH 0/4] Minor USB fixes Stefan Hajnoczi
2011-04-14 11:01 ` Stefan Hajnoczi
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=201104251102.17145.bradh@frogmouth.net \
--to=bradh@frogmouth.net \
--cc=hdegoede@redhat.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).