From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:43430 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932614Ab1ETCos (ORCPT ); Thu, 19 May 2011 22:44:48 -0400 Date: Thu, 19 May 2011 22:37:35 -0400 From: "John W. Linville" To: =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: linux-wireless@vger.kernel.org Subject: Re: wireless-next-2.6 freezing for merge window -- [sfr@canb.auug.org.au: linux-next: merge window reminder] Message-ID: <20110520023734.GA15919@tuxdriver.com> (sfid-20110520_044452_700796_0A57C08D) References: <20110519140421.GB2575@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, May 19, 2011 at 11:47:21PM +0200, Rafał Miłecki wrote: > 2011/5/19 John W. Linville : > > Please take note -- I will not be merging any additional patches > > in wireless-next-2.6 until the end of the merge window.  In fact, > > I will probably be backing-out a few that are already there. > > > > Fixes are, of course, still welcome for wireless-2.6. > > I've tried asking on IRC and finding answer on > http://wireless.kernel.org/en/developers/process but without a > success. > > Can I expect recent/current patches to land in any tree before merge > window closes? If they are not fixes and are not already in wireless-next-2.6 then probably not. John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.