qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] block/stream.c: ensure copy always set
Date: Wed, 25 Sep 2013 10:41:08 +0200	[thread overview]
Message-ID: <20130925084108.GD26684@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <p1txha1ehm.fsf@linaro.org>

On Tue, Sep 24, 2013 at 03:27:49PM +0100, Alex Bennée wrote:
> 
> stefanha@redhat.com writes:
> 
> > On Mon, Sep 23, 2013 at 05:07:30PM +0100, alex.bennee@linaro.org wrote:
> >> From: Alex Bennée <alex@bennee.com>
> >> 
> >> 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

  reply	other threads:[~2013-09-25  8:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23 16:07 [Qemu-devel] [PATCH v2 0/0] .travis and minor compile fixes alex.bennee
2013-09-23 16:07 ` [Qemu-devel] [PATCH 1/3] .travis.yml: basic compile and check recipes alex.bennee
2013-09-23 16:07 ` [Qemu-devel] [PATCH 2/3] .travis.yml: greatly expand the coverage + more builds alex.bennee
2013-09-23 16:07 ` [Qemu-devel] [PATCH 3/3] block/stream.c: ensure copy always set alex.bennee
2013-09-24 12:06   ` Stefan Hajnoczi
2013-09-24 14:27     ` Alex Bennée
2013-09-25  8:41       ` Stefan Hajnoczi [this message]
2013-09-24 11:41 ` [Qemu-devel] [PATCH v2 0/0] .travis and minor compile fixes Stefan Hajnoczi
2013-09-24 14:19   ` Alex Bennée
2013-09-25  8:33     ` Stefan Hajnoczi
2013-09-24 12:07 ` 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=20130925084108.GD26684@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).