From: Anthony Liguori <anthony@codemonkey.ws>
To: Shahar Havivi <shaharh@redhat.com>
Cc: Dor Laor <dlaor@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] QError: New QERR_DEVICE_NOT_ENCRYPTED
Date: Wed, 17 Mar 2010 11:20:30 -0500 [thread overview]
Message-ID: <4BA1014E.9060805@codemonkey.ws> (raw)
In-Reply-To: <fb6a8be110590fa6e67c23dced166a5fc5c7a0aa.1267827125.git.shaharh@redhat.com>
On 03/05/2010 04:25 PM, Shahar Havivi wrote:
> Signed-off-by: Shahar Havivi<shaharh@redhat.com>
>
Applied. Thanks.
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 2f657f4..4e63a54 100644
> --- a/qerror.c
> +++ b/qerror.c
> @@ -49,6 +49,10 @@ static const QErrorStringTable qerror_table[] = {
> .desc = "The %(device) is encrypted",
> },
> {
> + .error_fmt = QERR_DEVICE_NOT_ENCRYPTED,
> + .desc = "Device '%(device)' is not encrypted",
> + },
> + {
> .error_fmt = QERR_DEVICE_LOCKED,
> .desc = "Device %(device) is locked",
> },
> diff --git a/qerror.h b/qerror.h
> index ee59615..b93fff6 100644
> --- a/qerror.h
> +++ b/qerror.h
> @@ -46,6 +46,9 @@ QError *qobject_to_qerror(const QObject *obj);
> #define QERR_DEVICE_ENCRYPTED \
> "{ 'class': 'DeviceEncrypted', 'data': { 'device': %s } }"
>
> +#define QERR_DEVICE_NOT_ENCRYPTED \
> + "{ 'class': 'DeviceNotEncrypted', 'data': { 'device': %s } }"
> +
> #define QERR_DEVICE_LOCKED \
> "{ 'class': 'DeviceLocked', 'data': { 'device': %s } }"
>
>
next prev parent reply other threads:[~2010-03-17 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 22:24 [Qemu-devel] [PATCH 0/2] Fix block_passwd monitor command error Shahar Havivi
2010-03-05 22:25 ` [Qemu-devel] [PATCH 1/2] QError: New QERR_DEVICE_NOT_ENCRYPTED Shahar Havivi
2010-03-17 16:20 ` Anthony Liguori [this message]
2010-03-05 22:26 ` [Qemu-devel] [PATCH 2/2] Wrong error message in block_passwd command Shahar Havivi
2010-03-08 8:46 ` [Qemu-devel] [PATCH 0/2] Fix block_passwd monitor command error Kevin Wolf
2010-03-08 20:48 ` Luiz Capitulino
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=4BA1014E.9060805@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=dlaor@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shaharh@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 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).