From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: Only fixes for 3.4 -- Re: new stuff for 3.4 needs to be posted _now_
Date: Mon, 19 Mar 2012 10:58:27 -0400 [thread overview]
Message-ID: <20120319145826.GA19742@tuxdriver.com> (raw)
In-Reply-To: <20120305190508.GD18128@tuxdriver.com>
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.
prev parent reply other threads:[~2012-03-19 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120319145826.GA19742@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).