From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/26] My block patches queue for 1.1
Date: Mon, 07 May 2012 14:44:01 +0200 [thread overview]
Message-ID: <4FA7C391.2080101@redhat.com> (raw)
In-Reply-To: <CAHFMJ7t5Spw8SfcHrDw-0CnDr-Oh8XehnK5rbzy3Sd0vMEKNXQ@mail.gmail.com>
Am 04.05.2012 18:20, schrieb Paolo Bonzini:
> On Thu, Apr 12, 2012 at 2:00 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Here is my block patches queue for 1.1.
>>
>> Patches 1-6 are cleanups to tools and aio.c that let filesystems
>> use timers when running under qemu-io.
>>
>> Patches 7-12 are bugfixes from last week's series, patches 13-14
>> are new.
>>
>> Patches 15-19 are fixes to qemu-io and qemu-iotests.
>>
>> Patches 20-22 are fixes to streaming. Patch 22 modifies it to
>> not stream unallocated areas of the base (see rationale in the
>> commit message). For this reason I'm including in this series
>> also patch 23, which implements is_allocated for raw-posix.
>>
>> Finally, patches 24-26 are small changes to streaming that move
>> some code outside block/stream.c for more general usage.
>
> Kevin, what should I do about these patches? It needs rebasing, but
> there are several bugfixes in here, and there are more that I need to
> submit. Some ideas about what I could do to help:
>
> - split it in chunks, and see where we get by the time of 1.1 (risk of
> not finding problems in late patches)
>
> - find patches that are in RHEL, prod RHEL reviewers for a Reviewed-by.
First of all, please make sure to have me in the CC list. I try to scan
qemu-devel regularly, but when I'm busy it can happen that I don't for
some days.
If the patches need rebasing, rebase and resend them. It would be good
if you can limit the list of patches required for 1.1, but if all of
them are true fixes, we can still get them merged. Splitting into chunks
isn't necessary, but it would be helpful if you could put them in the
order of their importance, so that applying the series partially still
makes sense if necessary. Review is always appreciated, but it doesn't
really affect what patches to send.
Kevin
next prev parent reply other threads:[~2012-05-07 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1334232076-19018-1-git-send-email-pbonzini@redhat.com>
2012-05-04 16:20 ` [Qemu-devel] [PATCH 00/26] My block patches queue for 1.1 Paolo Bonzini
2012-05-07 12:44 ` Kevin Wolf [this message]
[not found] ` <1334232076-19018-18-git-send-email-pbonzini@redhat.com>
2012-05-08 12:57 ` [Qemu-devel] [PATCH 17/26] qemu-io: fix the alloc command Kevin Wolf
2012-05-08 13:06 ` Paolo Bonzini
2012-05-08 13:16 ` Kevin Wolf
2012-05-08 14:13 ` Paolo Bonzini
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=4FA7C391.2080101@redhat.com \
--to=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--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).