From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: qcow2 error path tests
Date: Mon, 14 Jun 2010 11:53:45 +0200 [thread overview]
Message-ID: <4C15FC29.4010803@redhat.com> (raw)
In-Reply-To: <20100614093808.GA32451@lst.de>
Am 14.06.2010 11:38, schrieb Christoph Hellwig:
> On Fri, Jun 04, 2010 at 07:35:24PM +0200, Kevin Wolf wrote:
>> This adds test cases for qcow2 error paths (using blkdebug)
>
> Thanks, applied.
>
> What's the plan for getting the fixes this tests into mainline?
The test passes in the block branch, but Anthony hasn't pulled for a
while now.
I'm not sure how to handle it, I have about 50 patches in the queue now
- if I want to send pull requests of resonable sizes it will take two
more pulls after the currently pending pull request of the week before
last. Of course I could just send all 50 patches at once, but I guess
he'd be even more uncomfortable with pulling then...
Anthony, what's your plan and what can I do to support you?
Kevin
prev parent reply other threads:[~2010-06-14 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 17:35 [Qemu-devel] [PATCH] qemu-iotests: qcow2 error path tests Kevin Wolf
2010-06-14 9:38 ` Christoph Hellwig
2010-06-14 9:53 ` 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=4C15FC29.4010803@redhat.com \
--to=kwolf@redhat.com \
--cc=hch@lst.de \
--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).