From: Anthony Liguori <anthony@codemonkey.ws>
To: Amos Kong <akong@redhat.com>
Cc: aliguori@us.ibm.com, eblake@redhat.com, qemu-devel@nongnu.org,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/6] qerror: add QERR_OVERFLOW
Date: Mon, 04 Jun 2012 13:27:02 +0800 [thread overview]
Message-ID: <4FCC4726.8020606@codemonkey.ws> (raw)
In-Reply-To: <1338591268-23962-2-git-send-email-akong@redhat.com>
On 06/02/2012 06:54 AM, Amos Kong wrote:
> Signed-off-by: Amos Kong<akong@redhat.com>
I think QERR_INVALID_PARAMETER_VALUE is a more logical choice for the error
you're generating.
Regards,
Anthony Liguori
> ---
> qerror.c | 4 ++++
> qerror.h | 3 +++
> 2 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/qerror.c b/qerror.c
> index 5092fe7..b66af09 100644
> --- a/qerror.c
> +++ b/qerror.c
> @@ -172,6 +172,10 @@ static const QErrorStringTable qerror_table[] = {
> .desc = "Parameter '%(name)' expects %(expected)",
> },
> {
> + .error_fmt = QERR_OVERFLOW,
> + .desc = "Input is overflow",
> + },
> + {
> .error_fmt = QERR_INVALID_PASSWORD,
> .desc = "Password incorrect",
> },
> diff --git a/qerror.h b/qerror.h
> index 4cbba48..dfe9c89 100644
> --- a/qerror.h
> +++ b/qerror.h
> @@ -151,6 +151,9 @@ QError *qobject_to_qerror(const QObject *obj);
> #define QERR_INVALID_PARAMETER_VALUE \
> "{ 'class': 'InvalidParameterValue', 'data': { 'name': %s, 'expected': %s } }"
>
> +#define QERR_OVERFLOW \
> + "{ 'class': 'Overflow', 'data': {} }"
> +
> #define QERR_INVALID_PASSWORD \
> "{ 'class': 'InvalidPassword', 'data': {} }"
>
next prev parent reply other threads:[~2012-06-04 5:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 22:54 [Qemu-devel] [PATCH v2 0/6] convert sendkey to qapi Amos Kong
2012-06-01 22:54 ` [Qemu-devel] [PATCH v2 1/6] qerror: add QERR_OVERFLOW Amos Kong
2012-06-04 5:27 ` Anthony Liguori [this message]
2012-06-05 14:29 ` [Qemu-devel] [PATCH v2 1/6] qerror: add MAX_KEYCODES 16 Amos Kong
[not found] ` <4FD0326F.3010806@redhat.com>
[not found] ` <20120611140642.06be2ee8@doriath.home>
[not found] ` <4FD62827.4060900@us.ibm.com>
[not found] ` <20120611142546.66871522@doriath.home>
2012-06-14 10:20 ` Amos Kong
2012-06-15 7:46 ` Amos Kong
2012-06-15 7:57 ` Gerd Hoffmann
2012-06-15 13:35 ` Luiz Capitulino
2012-06-18 15:30 ` Amos Kong
2012-06-19 9:52 ` Amos Kong
2012-06-01 22:54 ` [Qemu-devel] [PATCH v2 2/6] fix doc of using raw values with sendkey Amos Kong
2012-06-06 18:16 ` Luiz Capitulino
2012-06-01 22:54 ` [Qemu-devel] [PATCH v2 3/6] rename keyname '<' to 'less' Amos Kong
2012-06-06 18:22 ` Luiz Capitulino
2012-06-06 23:12 ` Amos Kong
2012-06-01 22:54 ` [Qemu-devel] [PATCH v2 4/6] hmp: rename arguments Amos Kong
2012-06-01 22:54 ` [Qemu-devel] [PATCH v2 5/6] qapi: generate list struct and visit_list for enum Amos Kong
2012-06-05 15:01 ` Amos Kong
2012-06-06 18:40 ` Luiz Capitulino
2012-06-07 0:26 ` Michael Roth
2012-06-07 2:52 ` Amos Kong
2012-06-11 17:00 ` Luiz Capitulino
2012-06-07 0:15 ` Michael Roth
2012-06-07 3:33 ` Amos Kong
2012-06-01 22:54 ` [Qemu-devel] [PATCH v2 6/6] qapi: convert sendkey Amos Kong
2012-06-04 17:09 ` Eric Blake
2012-06-05 14:55 ` Amos Kong
2012-06-05 15:05 ` Eric Blake
2012-06-06 7:13 ` Amos Kong
2012-06-06 11:58 ` Eric Blake
2012-06-07 4:51 ` Anthony Liguori
2012-06-07 13:08 ` Eric Blake
2012-06-01 23:03 ` [Qemu-devel] [PATCH v2 0/6] convert sendkey to qapi 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=4FCC4726.8020606@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=eblake@redhat.com \
--cc=lcapitulino@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).