Re: [Qemu-devel] [PATCH] qemu-char: Print strerror message on failure

2011-07-23 Thread Anthony Liguori
On 06/01/2011 06:29 AM, Kevin Wolf wrote: The only way for chardev drivers to communicate an error was to return a NULL pointer, which resulted in an error message that said _that_ something went wrong, but not _why_. This patch changes the interface to return 0/-errno and updates qemu_chr_open_

Re: [Qemu-devel] [PATCH] qemu-char: Print strerror message on failure

2011-06-22 Thread Anthony Liguori
On 06/21/2011 11:18 AM, Kevin Wolf wrote: Am 21.06.2011 18:09, schrieb Markus Armbruster: Kevin Wolf writes: The only way for chardev drivers to communicate an error was to return a NULL pointer, which resulted in an error message that said _that_ something went wrong, but not _why_. This pa

Re: [Qemu-devel] [PATCH] qemu-char: Print strerror message on failure

2011-06-21 Thread Markus Armbruster
Kevin Wolf writes: > The only way for chardev drivers to communicate an error was to return a NULL > pointer, which resulted in an error message that said _that_ something went > wrong, but not _why_. > > This patch changes the interface to return 0/-errno and updates > qemu_chr_open_opts to use

Re: [Qemu-devel] [PATCH] qemu-char: Print strerror message on failure

2011-06-21 Thread Kevin Wolf
Am 21.06.2011 18:09, schrieb Markus Armbruster: > Kevin Wolf writes: > >> The only way for chardev drivers to communicate an error was to return a NULL >> pointer, which resulted in an error message that said _that_ something went >> wrong, but not _why_. >> >> This patch changes the interface to

Re: [Qemu-devel] [PATCH] qemu-char: Print strerror message on failure

2011-06-21 Thread Kevin Wolf
Am 01.06.2011 13:29, schrieb Kevin Wolf: > The only way for chardev drivers to communicate an error was to return a NULL > pointer, which resulted in an error message that said _that_ something went > wrong, but not _why_. > > This patch changes the interface to return 0/-errno and updates > qemu_