From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Amos Kong <akong@redhat.com>
Cc: aliguori@us.ibm.com, quintela@redhat.com, jasowang@redhat.com,
qemu-devel@nongnu.org, owasserm@redhat.com, laine@redhat.com
Subject: Re: [Qemu-devel] [PATCH v11 1/4] qerror: add five qerror strings
Date: Thu, 10 May 2012 11:00:46 -0500 [thread overview]
Message-ID: <20120510160046.GB17353@illuin> (raw)
In-Reply-To: <20120508145822.4027.29292.stgit@t>
On Tue, May 08, 2012 at 10:58:22PM +0800, Amos Kong wrote:
> Add five new qerror strings, they are about listen/connect socket:
> QERR_SOCKET_CONNECT_IN_PROGRESS
> QERR_SOCKET_CONNECT_FAILED
> QERR_SOCKET_LISTEN_FAILED
> QERR_SOCKET_BIND_FAILED
> QERR_SOCKET_CREATE_FAILED
>
> Signed-off-by: Amos Kong <akong@redhat.com>
> Reviewed-by: Orit Wasserman <owasserm@redhat.com>
http://permalink.gmane.org/gmane.comp.emulators.qemu/146969
> ---
> qerror.c | 20 ++++++++++++++++++++
> qerror.h | 15 +++++++++++++++
> 2 files changed, 35 insertions(+), 0 deletions(-)
>
> diff --git a/qerror.c b/qerror.c
> index 96fbe71..2963b8c 100644
> --- a/qerror.c
> +++ b/qerror.c
> @@ -304,6 +304,26 @@ static const QErrorStringTable qerror_table[] = {
> .error_fmt = QERR_VNC_SERVER_FAILED,
> .desc = "Could not start VNC server on %(target)",
> },
> + {
> + .error_fmt = QERR_SOCKET_CONNECT_IN_PROGRESS,
> + .desc = "Connection can not be completed immediately",
> + },
> + {
> + .error_fmt = QERR_SOCKET_CONNECT_FAILED,
> + .desc = "Failed to connect socket",
> + },
> + {
> + .error_fmt = QERR_SOCKET_LISTEN_FAILED,
> + .desc = "Failed to listen socket",
> + },
> + {
> + .error_fmt = QERR_SOCKET_BIND_FAILED,
> + .desc = "Failed to bind socket",
> + },
> + {
> + .error_fmt = QERR_SOCKET_CREATE_FAILED,
> + .desc = "Failed to create socket",
> + },
> {}
> };
>
> diff --git a/qerror.h b/qerror.h
> index 5c23c1f..4cbba48 100644
> --- a/qerror.h
> +++ b/qerror.h
> @@ -248,4 +248,19 @@ QError *qobject_to_qerror(const QObject *obj);
> #define QERR_VNC_SERVER_FAILED \
> "{ 'class': 'VNCServerFailed', 'data': { 'target': %s } }"
>
> +#define QERR_SOCKET_CONNECT_IN_PROGRESS \
> + "{ 'class': 'SockConnectInprogress', 'data': {} }"
> +
> +#define QERR_SOCKET_CONNECT_FAILED \
> + "{ 'class': 'SockConnectFailed', 'data': {} }"
> +
> +#define QERR_SOCKET_LISTEN_FAILED \
> + "{ 'class': 'SockListenFailed', 'data': {} }"
> +
> +#define QERR_SOCKET_BIND_FAILED \
> + "{ 'class': 'SockBindFailed', 'data': {} }"
> +
> +#define QERR_SOCKET_CREATE_FAILED \
> + "{ 'class': 'SockCreateFailed', 'data': {} }"
> +
> #endif /* QERROR_H */
>
next prev parent reply other threads:[~2012-05-10 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 14:58 [Qemu-devel] [PATCH v11 0/4] support to migrate with IPv6 address Amos Kong
2012-05-08 14:58 ` [Qemu-devel] [PATCH v11 1/4] qerror: add five qerror strings Amos Kong
2012-05-10 16:00 ` Michael Roth [this message]
2012-05-08 14:58 ` [Qemu-devel] [PATCH v11 2/4] sockets: change inet_connect() to support nonblock socket Amos Kong
2012-05-08 14:58 ` [Qemu-devel] [PATCH v11 3/4] sockets: use error class to pass listen error Amos Kong
2012-05-10 16:03 ` Michael Roth
2012-05-08 14:58 ` [Qemu-devel] [PATCH v11 4/4] use inet_listen()/inet_connect() to support ipv6 migration Amos Kong
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=20120510160046.GB17353@illuin \
--to=mdroth@linux.vnet.ibm.com \
--cc=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jasowang@redhat.com \
--cc=laine@redhat.com \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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.