From: Kevin Wolf <kwolf@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] qcow2: More error path fixes
Date: Sat, 10 Apr 2010 10:13:49 +0200 [thread overview]
Message-ID: <4BC0333D.9070407@redhat.com> (raw)
In-Reply-To: <20100410000207.GR21042@volta.aurel32.net>
Am 10.04.2010 02:02, schrieb Aurelien Jarno:
> On Tue, Apr 06, 2010 at 03:30:08PM +0200, Kevin Wolf wrote:
>> This is part three of the qcow2 error path fixes. More to come...
>>
>> May depend on any patches sent earlier that are in my queue (I think it does
>> depend at least on the blkdebug series to apply cleanly)
>
> All those patches looks fine to me, but as you explained, they depend
> on the blkdebug series, that I am not fully comfortable to review.
>
> I have therefore applied patches 1 & 6 only, to be able to cherry-pick
> them to the stable branch.
Okay, makes sense. The patches you left out are nice to have, but not as
critical as 1 & 6, so that's fine. Block work can be done based on my
tree, so it doesn't hurt too much if they sit on the list until Anthony
returns.
Kevin
prev parent reply other threads:[~2010-04-10 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 13:30 [Qemu-devel] [PATCH 0/6] qcow2: More error path fixes Kevin Wolf
2010-04-06 13:30 ` [Qemu-devel] [PATCH 1/6] qcow2: Don't ignore immediate read/write failures Kevin Wolf
2010-04-06 13:30 ` [Qemu-devel] [PATCH 2/6] qcow2: Return 0/-errno in write_l2_entries Kevin Wolf
2010-04-06 13:30 ` [Qemu-devel] [PATCH 3/6] qcow2: Fix error return code in qcow2_alloc_cluster_link_l2 Kevin Wolf
2010-04-06 13:30 ` [Qemu-devel] [PATCH 4/6] qcow2: Return 0/-errno in write_l1_entry Kevin Wolf
2010-04-06 13:30 ` [Qemu-devel] [PATCH 5/6] qcow2: Return 0/-errno in l2_allocate Kevin Wolf
2010-04-06 13:30 ` [Qemu-devel] [PATCH 6/6] qcow2: Remove request from in-flight list after error Kevin Wolf
2010-04-10 0:02 ` [Qemu-devel] [PATCH 0/6] qcow2: More error path fixes Aurelien Jarno
2010-04-10 8:13 ` Kevin Wolf [this message]
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=4BC0333D.9070407@redhat.com \
--to=kwolf@redhat.com \
--cc=aurelien@aurel32.net \
--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).