From: Stefan Hajnoczi <stefanha@gmail.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] block: use proper qerrors in qmp_block_resize
Date: Wed, 4 Jan 2012 22:21:39 +0000 [thread overview]
Message-ID: <CAJSP0QU2HoF9rPeF3RW--KRR2Z2UxDLr2T7cQy43_8sh47G+cw@mail.gmail.com> (raw)
In-Reply-To: <20120104175931.488b5fc6@doriath>
On Wed, Jan 4, 2012 at 7:59 PM, Luiz Capitulino <lcapitulino@redhat.com> wrote:
> On Wed, 4 Jan 2012 17:38:23 +0000
> Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> wrote:
>
>> Let's report specific errors so that management tools and users can
>> identify the problem.
>>
>> Two new qerrors are needed:
>> * QERR_DEVICE_HAS_NO_MEDIUM for ENOMEDIUM
>> * QERR_DEVICE_IS_READ_ONLY for EACCES
>
> Great series, the number of complaints about generic errors have increased
> lately. It's to fix this.
>
> There's a missing bit though, would you mind to update the block_resize's
> command documentation in the schema?
Sure, fixed in v2.
next prev parent reply other threads:[~2012-01-04 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 17:38 [Qemu-devel] [PATCH 0/3] qerror: proper errors for qmp_block_resize() Stefan Hajnoczi
2012-01-04 17:38 ` [Qemu-devel] [PATCH 1/3] qerror: add check-qerror.sh to verify alphabetical order Stefan Hajnoczi
2012-01-04 17:38 ` [Qemu-devel] [PATCH 2/3] qerror: restore alphabetical order over qerrors Stefan Hajnoczi
2012-01-04 17:38 ` [Qemu-devel] [PATCH 3/3] block: use proper qerrors in qmp_block_resize Stefan Hajnoczi
2012-01-04 19:59 ` Luiz Capitulino
2012-01-04 22:21 ` Stefan Hajnoczi [this message]
2012-01-04 20:01 ` [Qemu-devel] [PATCH 0/3] qerror: proper errors for qmp_block_resize() Luiz Capitulino
2012-01-04 21:58 ` Stefan Hajnoczi
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=CAJSP0QU2HoF9rPeF3RW--KRR2Z2UxDLr2T7cQy43_8sh47G+cw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).