From: "Rafał Miłecki" <zajec5@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wireless-next-2.6 freezing for merge window -- [sfr@canb.auug.org.au: linux-next: merge window reminder]
Date: Thu, 19 May 2011 23:47:21 +0200 [thread overview]
Message-ID: <BANLkTi=Qve-02HPB_c6WZMaE1f0qWCBTwA@mail.gmail.com> (raw)
In-Reply-To: <20110519140421.GB2575@tuxdriver.com>
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ł
next prev parent reply other threads:[~2011-05-19 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2011-05-20 2:37 ` John W. Linville
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='BANLkTi=Qve-02HPB_c6WZMaE1f0qWCBTwA@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).