From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: [README] Merge window has openned
Date: Mon, 01 Oct 2012 00:53:53 -0400 (EDT) [thread overview]
Message-ID: <20121001.005353.1893936334196650641.davem@davemloft.net> (raw)
You all know what this means.
Anything not in patchwork already is not going to make it into this
merge window.
I'm allowing a minor exception for the bnx2x driver firmware update
which needs a respin to fix build errors.
Please do not submit new features until the merge window closes and I
reopen net-next for development. Do not ask me for an exception, the
net-next tree was open for about two months.
Bug fixes may be submitted at any time.
I intend to send a pull request to Linus for net-next on Wednesday.
This assumes I can work through the patchwork backlog and get the
bnx2x respin by the end of Monday so that everything gets at least one
day of exposure in linux-next. So if things don't fall into place by
Monday night I'll push the pull request back a day or two, as needed.
Thanks.
reply other threads:[~2012-10-01 4:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121001.005353.1893936334196650641.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).