* new stuff for 3.4 needs to be posted _now_
@ 2012-03-05 19:05 John W. Linville
2012-03-19 14:58 ` Only fixes for 3.4 -- " John W. Linville
0 siblings, 1 reply; 2+ messages in thread
From: John W. Linville @ 2012-03-05 19:05 UTC (permalink / raw)
To: linux-wireless
You may have noticed that Linus has released 3.3-rc6, and doesn't
necessarily plan to go beyond -rc7. 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 3.4. In fact, any non-fix patches need to
already be in wireless-next when the merge window opens if you want
them in 3.4. 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 have been warned...this means you!
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] 2+ messages in thread
* Only fixes for 3.4 -- Re: new stuff for 3.4 needs to be posted _now_
2012-03-05 19:05 new stuff for 3.4 needs to be posted _now_ John W. Linville
@ 2012-03-19 14:58 ` John W. Linville
0 siblings, 0 replies; 2+ messages in thread
From: John W. Linville @ 2012-03-19 14:58 UTC (permalink / raw)
To: linux-wireless
On Mon, Mar 05, 2012 at 02:05:08PM -0500, John W. Linville wrote:
> You may have noticed that Linus has released 3.3-rc6, and doesn't
> necessarily plan to go beyond -rc7. 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 3.4. In fact, any non-fix patches need to
> already be in wireless-next when the merge window opens if you want
> them in 3.4. 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 have been warned...this means you!
Linus released 3.3 yesterday (Sunday, 3/18). The merge window for
the mainline kernel is open.
Anything not already merged in wireless-next (or wireless-testing)
will not be merged for 3.4 unless it is a fix. If you have already
posted a fix that is not clearly marked as such, then you might send
me a reminder about it. Otherwise, patches will have to wait for 3.5.
Merging for 3.5 will not occur after the close of the merge window
(~2 weeks from now). Please plan accordingly.
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] 2+ messages in thread
end of thread, other threads:[~2012-03-19 15:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-05 19:05 new stuff for 3.4 needs to be posted _now_ John W. Linville
2012-03-19 14:58 ` Only fixes for 3.4 -- " 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).