From: Kalle Valo <kvalo@codeaurora.org>
To: linux-wireless@vger.kernel.org
Subject: wireless-drivers-next is closed for 4.10
Date: Thu, 08 Dec 2016 14:53:23 +0200 [thread overview]
Message-ID: <87twae4m64.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87oa0zwymr.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Mon, 28 Nov 2016 14:57:16 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> Linus said that he will release 4.9 either next Sunday or a week after,
> which means that the merge window is getting close. If there's something
> you absolutely need to have in 4.10 better send them NOW to not miss the
> window.
Dave closed net-next earlier than normally so wireless-drivers-next is
closed as well:
https://www.spinics.net/lists/netdev/msg409280.html
I had two patches pending in w-d-next but now I'll need to submit those
to net-next after the merge window and they will go to 4.11.
> Important bug fixes can go to 4.10 also after the merge window, but not
> new features.
wireless-drivers is open for bug fixes going to 4.10.
--
Kalle Valo
prev parent reply other threads:[~2016-12-08 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 12:57 wireless-drivers-next soon closing for 4.10 Kalle Valo
2016-12-08 12:53 ` Kalle Valo [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=87twae4m64.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--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).