From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, fromani@redhat.com, stefanha@redhat.com,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: Fix block-set-write-threshold not to use funky error class
Date: Fri, 13 Mar 2015 13:11:54 -0600 [thread overview]
Message-ID: <5503367A.5090308@redhat.com> (raw)
In-Reply-To: <1426269098-16043-1-git-send-email-armbru@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On 03/13/2015 11:51 AM, Markus Armbruster wrote:
> Error classes are a leftover from the days of "rich" error objects.
> New code should always use ERROR_CLASS_GENERIC_ERROR.
More precisely, new code should use ERROR_CLASS_GENERIC_ERROR unless
there is a good reason where a caller knowing a different error class is
likely to react differently as a result (for example, with
'drive-mirror', libvirt DOES rely on QERR_DEVICE_NOT_FOUND as a witness
that the command supports an optional 'top' argument, vs.
ERROR_CLASS_GENERIC_ERROR to state that 'top' was still mandatory).
But I agree that this situation is one unlikely to be where libvirt
cares what error class was used.
> Commit e246211
> added a use of ERROR_CLASS_DEVICE_NOT_FOUND. Replace it.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> block/write-threshold.c | 2 +-
> qapi/block-core.json | 4 ----
> 2 files changed, 1 insertion(+), 5 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-03-13 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 17:51 [Qemu-devel] [PATCH] block: Fix block-set-write-threshold not to use funky error class Markus Armbruster
2015-03-13 19:11 ` Eric Blake [this message]
2015-03-13 20:17 ` Markus Armbruster
2015-03-16 15:04 ` Kevin Wolf
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=5503367A.5090308@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=fromani@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).