From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: linux-next: manual merge of the lost-spurious-irq tree with the tip tree Date: Tue, 5 Oct 2010 09:01:23 +0200 Message-ID: <20101005070123.GF12267@elte.hu> References: <20101005141334.6a0f15fd.sfr@canb.auug.org.au> <4CAABC0E.3030700@kernel.org> <20101005063227.GB12267@elte.hu> <20101005174524.b62d14a1.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:37244 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754788Ab0JEHEp (ORCPT ); Tue, 5 Oct 2010 03:04:45 -0400 Content-Disposition: inline In-Reply-To: <20101005174524.b62d14a1.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Tejun Heo , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner , "H. Peter Anvin" , Peter Zijlstra * Stephen Rothwell wrote: > Not sure what I can do beyond making sure that all relevant people are > informed about what trees are being merged. [...] Fortunately there's a really simple solution: wait for an explicit reply from a maintainer before adding a new-feature tree. (Solicite again via a To: email if the Cc: went unanswered by the maintainers.) Could you please start using that method for all subsystems i co-maintain? Thanks, Ingo