From: Markus Armbruster <armbru@redhat.com>
To: Mao Zhongyi <maozy.fnst@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, jasowang@redhat.com
Subject: Re: [Qemu-devel] [PATCH v8 2/4] net/socket: Convert several helper functions to Error
Date: Thu, 06 Jul 2017 09:21:54 +0200 [thread overview]
Message-ID: <878tk29gj1.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <dead2942a713810709c6ed8cbafc7381bee5d08f.1499250206.git.maozy.fnst@cn.fujitsu.com> (Mao Zhongyi's message of "Wed, 5 Jul 2017 19:01:55 +0800")
Mao Zhongyi <maozy.fnst@cn.fujitsu.com> writes:
> Currently, net_socket_mcast_create(), net_socket_fd_init_dgram() and
> net_socket_fd_init() use the function such as fprintf(), perror() to
> report an error message.
>
> Now, convert these functions to Error.
>
> Cc: jasowang@redhat.com
> Cc: armbru@redhat.com
> Cc: berrange@redhat.com
> Signed-off-by: Mao Zhongyi <maozy.fnst@cn.fujitsu.com>
> Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2017-07-06 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 11:01 [Qemu-devel] [PATCH v8 0/4] Improve error reporting Mao Zhongyi
2017-07-05 11:01 ` [Qemu-devel] [PATCH v8 1/4] net/socket: Don't treat odd socket type as SOCK_STREAM Mao Zhongyi
2017-07-05 11:01 ` [Qemu-devel] [PATCH v8 2/4] net/socket: Convert several helper functions to Error Mao Zhongyi
2017-07-06 7:21 ` Markus Armbruster [this message]
2017-07-05 11:01 ` [Qemu-devel] [PATCH v8 3/4] net/net: Convert parse_host_port() " Mao Zhongyi
2017-07-05 11:01 ` [Qemu-devel] [PATCH v8 4/4] net/socket: Improve -net socket error reporting Mao Zhongyi
2017-07-06 7:24 ` Markus Armbruster
2017-07-06 8:07 ` Mao Zhongyi
-- strict thread matches above, loose matches on Subject: below --
2017-07-06 8:47 [Qemu-devel] [PATCH v8 0/4] Improve " Mao Zhongyi
2017-07-06 8:47 ` [Qemu-devel] [PATCH v8 2/4] net/socket: Convert several helper functions to Error Mao Zhongyi
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=878tk29gj1.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=jasowang@redhat.com \
--cc=maozy.fnst@cn.fujitsu.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 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.