From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47205) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VOkeq-0001tl-GF for qemu-devel@nongnu.org; Wed, 25 Sep 2013 04:41:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VOkem-0004kx-BR for qemu-devel@nongnu.org; Wed, 25 Sep 2013 04:41:16 -0400 Received: from mail-ea0-x231.google.com ([2a00:1450:4013:c01::231]:46742) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VOkem-0004kr-4D for qemu-devel@nongnu.org; Wed, 25 Sep 2013 04:41:12 -0400 Received: by mail-ea0-f177.google.com with SMTP id f15so3018094eak.36 for ; Wed, 25 Sep 2013 01:41:11 -0700 (PDT) Date: Wed, 25 Sep 2013 10:41:08 +0200 From: Stefan Hajnoczi Message-ID: <20130925084108.GD26684@stefanha-thinkpad.redhat.com> References: <1379952450-29640-1-git-send-email-alex.bennee@linaro.org> <1379952450-29640-4-git-send-email-alex.bennee@linaro.org> <20130924120628.GF27882@stefanha-thinkpad.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Subject: Re: [Qemu-devel] [PATCH 3/3] block/stream.c: ensure copy always set List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex =?iso-8859-1?Q?Benn=E9e?= Cc: kwolf@redhat.com, qemu-devel@nongnu.org, Stefan Hajnoczi 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 > >> > >> This only showed up when compiling with > >> --enable-trace-backend=stderr|ftrace at which point the compiler > >> complains with the following: > > > > > 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