From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: Re: linux-next: reminder Date: Wed, 10 Jul 2013 09:44:58 +0300 Message-ID: <51DD02EA.9010909@kernel.org> References: <20130702170957.17c3173584fcdef073bf4a6b@canb.auug.org.au> <20130710100707.d79b5df2a826faf1caecf3b4@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-lb0-f170.google.com ([209.85.217.170]:46951 "EHLO mail-lb0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750894Ab3GJGpC (ORCPT ); Wed, 10 Jul 2013 02:45:02 -0400 In-Reply-To: <20130710100707.d79b5df2a826faf1caecf3b4@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Christoph Lameter On 07/10/2013 03:07 AM, Stephen Rothwell wrote: > Hi all, > > On Tue, 2 Jul 2013 17:09:57 +1000 Stephen Rothwell wrote: >> >> We are in the merge window, so please do not add anything to your >> linux-next included branches that is not destined for v3.11 until after >> v3.11-rc1 is released. > > No, really :-( > > i.e. maintainers should be saying "No" to any "features" that were not > ready before the merge window opened (even when the maintainer and the > developer are the same person) ... It's being queued for v3.11. I was on vacation for two weeks with no internet at the worst possible moment and I was backlogged with slab patches. Sorry for breaking things! Pekka