* wireless-next-2.6 freezing for merge window -- [sfr@canb.auug.org.au: linux-next: merge window reminder]
@ 2011-05-19 14:04 John W. Linville
2011-05-19 21:47 ` Rafał Miłecki
0 siblings, 1 reply; 3+ messages in thread
From: John W. Linville @ 2011-05-19 14:04 UTC (permalink / raw)
To: linux-wireless
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.
John
----- Forwarded message from Stephen Rothwell <sfr@canb.auug.org.au> -----
> Date: Thu, 19 May 2011 16:43:23 +1000
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> To: LKML <linux-kernel@vger.kernel.org>
> Cc: linux-next@vger.kernel.org
> Subject: linux-next: merge window reminder
> X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.4; i486-pc-linux-gnu)
>
> Hi all,
>
> Please remember that I do not want any v2.6.41 related stuff in
> linux-next included trees until after v2.6.40-rc1 has been released.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
----- End forwarded message -----
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: wireless-next-2.6 freezing for merge window -- [sfr@canb.auug.org.au: linux-next: merge window reminder]
2011-05-19 14:04 wireless-next-2.6 freezing for merge window -- [sfr@canb.auug.org.au: linux-next: merge window reminder] John W. Linville
@ 2011-05-19 21:47 ` Rafał Miłecki
2011-05-20 2:37 ` John W. Linville
0 siblings, 1 reply; 3+ messages in thread
From: Rafał Miłecki @ 2011-05-19 21:47 UTC (permalink / raw)
To: John W. Linville; +Cc: linux-wireless
2011/5/19 John W. Linville <linville@tuxdriver.com>:
> 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?
--
Rafał
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: wireless-next-2.6 freezing for merge window -- [sfr@canb.auug.org.au: linux-next: merge window reminder]
2011-05-19 21:47 ` Rafał Miłecki
@ 2011-05-20 2:37 ` John W. Linville
0 siblings, 0 replies; 3+ messages in thread
From: John W. Linville @ 2011-05-20 2:37 UTC (permalink / raw)
To: Rafał Miłecki; +Cc: linux-wireless
On Thu, May 19, 2011 at 11:47:21PM +0200, Rafał Miłecki wrote:
> 2011/5/19 John W. Linville <linville@tuxdriver.com>:
> > 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-05-20 2:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-19 14:04 wireless-next-2.6 freezing for merge window -- [sfr@canb.auug.org.au: linux-next: merge window reminder] John W. Linville
2011-05-19 21:47 ` Rafał Miłecki
2011-05-20 2:37 ` John W. Linville
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).