From: Hans de Goede <hdegoede@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 14/14] usb: Proper error propagation for usb_device_attach errors
Date: Tue, 31 May 2011 12:13:11 +0200 [thread overview]
Message-ID: <4DE4BF37.2060402@redhat.com> (raw)
In-Reply-To: <4DE4BF17.8060602@redhat.com>
Hi,
On 05/31/2011 12:12 PM, Kevin Wolf wrote:
> Am 31.05.2011 12:05, schrieb Hans de Goede:
>> Hi,
>>
>> On 05/31/2011 11:56 AM, Kevin Wolf wrote:
>>> Am 31.05.2011 11:51, schrieb Hans de Goede:
>>>> Hi,
>>>>
>>>> On 05/31/2011 11:42 AM, Michael Tokarev wrote:
>>>>> 31.05.2011 13:35, Hans de Goede wrote:
>>>>>> ---
>>>>>> hw/usb-bus.c | 23 ++++++++++++-----------
>>>>>> hw/usb-msd.c | 5 +++--
>>>>>> usb-linux.c | 6 +++++-
>>>>>> 3 files changed, 20 insertions(+), 14 deletions(-)
>>>>>>
>>>>>> diff --git a/hw/usb-bus.c b/hw/usb-bus.c
>>>>>> index 0a49921..2ae2678 100644
>>>>>> --- a/hw/usb-bus.c
>>>>>> +++ b/hw/usb-bus.c
>>>>>
>>>>>> if (dev->attached) {
>>>>>> - fprintf(stderr, "Warning: tried to attach usb device %s twice\n",
>>>>>> + fprintf(stderr, "Error: tried to attach usb device %s twice\n",
>>>>>> dev->product_desc);
>>>>>
>>>>> qemu_error() maybe, while we're at it?
>>>>> Here and in a few other places.
>>>>
>>>> That does not seem to exist, do you perhaps mean error_printf() ?
>>>
>>> error_report() is what you should use, so that messages go to the
>>> monitor if the function is called from a monitor command. error_printf()
>>> is used by it internally, but usually isn't used directly.
>>>
>>
>> I've looked at error_report, but IMHO it is made of crazy, I'm not going
>> to construct a json dict every time I need to log some simple error message
>> (and the existing ones are not suitable for many error messages).
>
> error_report() works with plain strings. Maybe you confuse it with the
> QMP error reporting function?
Ah yes I was looking at qerror_report (who ever named that, having just
one letter difference in the function names is a bad idea). error_report
looks fine.
I'll wait a bit for more feedback and then change
[PATCH 14/14] usb: Proper error propagation for usb_device_attach errors
To turn the fprintf(stderr, ... calls into error_report calls.
Thanks & Regards,
Hans
>
> Kevin
>
next prev parent reply other threads:[~2011-05-31 10:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 9:35 [Qemu-devel] [PATCH 00/14] usb: various usb fixes Hans de Goede
2011-05-31 9:35 ` [Qemu-devel] [PATCH 01/14] usb-linux: Set usb_auto_timer to NULL after deleting it Hans de Goede
2011-06-01 10:48 ` Gerd Hoffmann
2011-06-01 14:24 ` Hans de Goede
2011-05-31 9:35 ` [Qemu-devel] [PATCH 02/14] usb-linux: Get speed from sysfs rather then from the connectinfo ioctl Hans de Goede
2011-06-01 11:25 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 03/14] usb-linux: Teach about super speed Hans de Goede
2011-06-01 11:28 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 04/14] usb-linux: Don't do perror when errno is not set Hans de Goede
2011-06-01 11:29 ` Gerd Hoffmann
2011-06-01 11:43 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 05/14] usb-linux: Don't call usb_host_close when usb_host_open fails Hans de Goede
2011-06-01 12:22 ` Gerd Hoffmann
2011-06-01 14:33 ` Hans de Goede
2011-05-31 9:35 ` [Qemu-devel] [PATCH 06/14] usb-linux: Ensure devep != 0 Hans de Goede
2011-06-01 12:24 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 07/14] usb-linux: If opening a device fails remove it from our filter list Hans de Goede
2011-06-01 12:32 ` Gerd Hoffmann
2011-06-01 14:37 ` Hans de Goede
2011-06-06 10:24 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 08/14] usb-linux: Don't try to open the same device twice Hans de Goede
2011-06-01 12:35 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 09/14] usb-linux: Don't declare a usbdevice_name Hans de Goede
2011-06-01 12:44 ` Gerd Hoffmann
2011-06-01 14:38 ` Hans de Goede
2011-05-31 9:35 ` [Qemu-devel] [PATCH 10/14] usb-linux: Enlarge buffer for descriptors to 8192 bytes Hans de Goede
2011-06-01 12:44 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 11/14] usb-bus: Add knowledge of USB_SPEED_SUPER to usb_speed helper Hans de Goede
2011-06-01 12:47 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 12/14] usb-bus: Don't allow attaching a device to a bus with no free ports Hans de Goede
2011-05-31 9:35 ` [Qemu-devel] [PATCH 13/14] usb-bus: Don't detach non attached devices on device exit Hans de Goede
2011-06-01 12:51 ` Gerd Hoffmann
2011-05-31 9:35 ` [Qemu-devel] [PATCH 14/14] usb: Proper error propagation for usb_device_attach errors Hans de Goede
2011-05-31 9:42 ` Michael Tokarev
2011-05-31 9:51 ` Hans de Goede
2011-05-31 9:56 ` Kevin Wolf
2011-05-31 10:05 ` Hans de Goede
2011-05-31 10:12 ` Kevin Wolf
2011-05-31 10:13 ` Hans de Goede [this message]
2011-06-01 12:50 ` Gerd Hoffmann
2011-06-01 14:42 ` Hans de Goede
2011-06-06 10:27 ` 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=4DE4BF37.2060402@redhat.com \
--to=hdegoede@redhat.com \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--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 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.