linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2009-06-10
Date: Wed, 10 Jun 2009 23:44:24 -0700 (PDT)	[thread overview]
Message-ID: <20090610.234424.69074010.davem@davemloft.net> (raw)
In-Reply-To: <20090610185639.GC3892@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 10 Jun 2009 14:56:39 -0400

> Despite my previous optimistic prediction, I need to ask for one more
> 2.6.31 pull before/during the merge window... :-)
> 
> This one actually does have a number of bug fixes embedded within, as
> well as some further fleshing-out and usage of the new rfkill
> infrastructure changes that are already queued for 2.6.31.  The other
> bits are more minor, but they have already spent at least a few days in
> -next and I believe they are safe for 2.6.31.

Pulled, I'll push out after some build verifications.

> P.S.  For some reason (probably the 2.6.30 release) the public push on
> kernel.org seems to be taking a lot longer than usual.  So you probably
> want to ensure that the wireless-next-2.6 head matches 2f0accc13520 or
> just pull using ssh (or direct file access).

I verified this, but you can sidestep this entire problem by simply
giving me master.kernel.org SSH based URLs to pull from. :-)


      reply	other threads:[~2009-06-11  6:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 18:56 pull request: wireless-next-2.6 2009-06-10 John W. Linville
2009-06-11  6:44 ` David Miller [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=20090610.234424.69074010.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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).