From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 04/11] error: New QERR_INVALID_PARAMETER_VALUE
Date: Fri, 19 Mar 2010 16:49:29 -0300 [thread overview]
Message-ID: <20100319164929.74810d16@redhat.com> (raw)
In-Reply-To: <1268929996-28763-5-git-send-email-armbru@redhat.com>
On Thu, 18 Mar 2010 17:33:11 +0100
Markus Armbruster <armbru@redhat.com> wrote:
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qerror.c | 4 ++++
> qerror.h | 3 +++
> 2 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/qerror.c b/qerror.c
> index 9fb817e..97e8d4a 100644
> --- a/qerror.c
> +++ b/qerror.c
> @@ -121,6 +121,10 @@ static const QErrorStringTable qerror_table[] = {
> .desc = "Invalid parameter type, expected: %(expected)",
> },
> {
> + .error_fmt = QERR_INVALID_PARAMETER_VALUE,
> + .desc = "Parameter '%(name)' expects %(expected)",
> + },
Would we need this error if we improve QERR_INVALID_PARAMETER to
accept an optional 'expects' parameter?
> + {
> .error_fmt = QERR_INVALID_PASSWORD,
> .desc = "Password incorrect",
> },
> diff --git a/qerror.h b/qerror.h
> index 870cdc3..5625d54 100644
> --- a/qerror.h
> +++ b/qerror.h
> @@ -106,6 +106,9 @@ QError *qobject_to_qerror(const QObject *obj);
> #define QERR_INVALID_PARAMETER_TYPE \
> "{ 'class': 'InvalidParameterType', 'data': { 'name': %s,'expected': %s } }"
>
> +#define QERR_INVALID_PARAMETER_VALUE \
> + "{ 'class': 'InvalidParameterValue', 'data': { 'name': %s, 'expected': %s } }"
> +
> #define QERR_INVALID_PASSWORD \
> "{ 'class': 'InvalidPassword', 'data': {} }"
>
next prev parent reply other threads:[~2010-03-19 19:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 16:33 [Qemu-devel] [PATCH 00/11] monitor: New commands netdev_add, netdev_del Markus Armbruster
2010-03-18 16:33 ` [Qemu-devel] [PATCH 01/11] error: Put error definitions back in alphabetical order Markus Armbruster
2010-03-18 16:33 ` [Qemu-devel] [PATCH 02/11] error: New QERR_DUPLICATE_ID Markus Armbruster
2010-03-18 16:33 ` [Qemu-devel] [PATCH 03/11] error: Convert qemu_opts_create() to QError Markus Armbruster
2010-03-18 16:33 ` [Qemu-devel] [PATCH 04/11] error: New QERR_INVALID_PARAMETER_VALUE Markus Armbruster
2010-03-19 19:49 ` Luiz Capitulino [this message]
2010-03-19 21:05 ` [Qemu-devel] " Markus Armbruster
2010-03-22 0:34 ` Luiz Capitulino
2010-03-18 16:33 ` [Qemu-devel] [PATCH 05/11] error: Convert qemu_opts_set() to QError Markus Armbruster
2010-03-19 19:50 ` [Qemu-devel] " Luiz Capitulino
2010-03-19 20:58 ` Markus Armbruster
2010-03-18 16:33 ` [Qemu-devel] [PATCH 06/11] error: Drop extra messages after qemu_opts_set() and qemu_opts_parse() Markus Armbruster
2010-03-18 16:33 ` [Qemu-devel] [PATCH 07/11] error: Use QERR_INVALID_PARAMETER_VALUE instead of QERR_INVALID_PARAMETER Markus Armbruster
2010-03-18 16:33 ` [Qemu-devel] [PATCH 08/11] error: Convert qemu_opts_validate() to QError Markus Armbruster
2010-03-18 16:33 ` [Qemu-devel] [PATCH 09/11] error: Convert net_client_init() " Markus Armbruster
2010-03-18 16:35 ` [Qemu-devel] [PATCH 10/11] error: New QERR_DEVICE_IN_USE Markus Armbruster
2010-03-18 16:35 ` [Qemu-devel] [PATCH 11/11] monitor: New commands netdev_add, netdev_del Markus Armbruster
2010-03-19 19:48 ` [Qemu-devel] Re: [PATCH 00/11] " Luiz Capitulino
2010-03-19 20:55 ` Markus Armbruster
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=20100319164929.74810d16@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@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 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.