From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from senator.holtmann.net ([87.106.208.187]:49034 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754462Ab0GXCXJ (ORCPT ); Fri, 23 Jul 2010 22:23:09 -0400 Subject: Re: new stuff for 2.6.36 needs to be posted _now_ From: Marcel Holtmann To: "John W. Linville" Cc: linux-wireless@vger.kernel.org In-Reply-To: <20100723204529.GE2426@tuxdriver.com> References: <20100723204529.GE2426@tuxdriver.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 23 Jul 2010 19:23:01 -0700 Message-ID: <1279938181.2621.22.camel@localhost.localdomain> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi John, > You may have noticed that when Linus released 2.6.35-rc6, he > optimistically predicted that it will be the last -rc for 2.6.35. > So, the merge window is around the corner! > > For those that need a reminder, the opening of the merge window is a > _deadline_ for new features. Once the merge window opens, only fixes > will be accepted for 2.6.36. In fact, any non-fix patches need to > already be in wireless-next-2.6 when the merge window opens if you want > them in 2.6.36. That means you need to get them posted _now_, so they > can be reviewed and I can find time to merge them before the deadline. you did see my pull request for bluetooth-next-2.6 tree? I have two additional patches that should go in, but I wait until you pulled that one first. Regards Marcel