[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 3/3] block/stream.c: ensure copy always set
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [PATCH 3/3] block/stream.c: ensure copy always set |
Date: |
Wed, 25 Sep 2013 10:41:08 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Tue, Sep 24, 2013 at 03:27:49PM +0100, Alex Bennée wrote:
>
> address@hidden writes:
>
> > On Mon, Sep 23, 2013 at 05:07:30PM +0100, address@hidden wrote:
> >> From: Alex Bennée <address@hidden>
> >>
> >> This only showed up when compiling with
> >> --enable-trace-backend=stderr|ftrace at which point the compiler
> >> complains with the following:
> <nsip>
> >
> > Stefan Weil already posted a similar patch:
> > http://patchwork.ozlabs.org/patch/276936/
>
> OK I'll drop the patch in v3 which I guess is getting ready to be a
> proper PULL request ;-)
You don't need to send a pull request yourself. Once your patch is
reviewed it should be merged by a maintainer.
> What's the typical lag for trivial patches getting in? I see there are
> periodic trivial pull requests. I assume there are maintainers that
> collect these up into trees?
Contributors send patches to qemu-devel. After the patches are reviewed
they are merged either directly into qemu.git or into a subsystem tree
by a maintainer.
Subsystem maintainers send pull requests to flush their patch queue when
they feel it is appropriate. For example, Kevin and I send a weekly
block layer pull request that usually contains 5-15 patches.
Expect 1.5 weeks to get the average patch reviewed and merged into
qemu.git. If you're lucky they can be merged in a day. If you're
unlucky you may have to ping the list to move the process along.
Stefan