All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.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 22:37:35 -0400	[thread overview]
Message-ID: <20110520023734.GA15919@tuxdriver.com> (raw)
In-Reply-To: <BANLkTi=Qve-02HPB_c6WZMaE1f0qWCBTwA@mail.gmail.com>

On Thu, May 19, 2011 at 11:47:21PM +0200, Rafał Miłecki wrote:
> 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?

If they are not fixes and are not already in wireless-next-2.6 then
probably not.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2011-05-20  2:44 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
2011-05-20  2:37   ` 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=20110520023734.GA15919@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.