All of lore.kernel.org
 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
Subject: Re: pull request: wireless-next-2.6 2011-03-11
Date: Sat, 12 Mar 2011 14:40:32 -0800 (PST)	[thread overview]
Message-ID: <20110312.144032.71127259.davem@davemloft.net> (raw)
In-Reply-To: <20110311210614.GF14583@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 11 Mar 2011 16:06:14 -0500

> Welcome to this week's installment of updates from the wireless world
> intended for 2.6.39... :-)  The biggest notables here are a bluetooth
> pull from Gustavo, a wl12xx pull from Luca, and a number of rt2x00
> updates, along with the usual smattering of various driver updates
> and small enhancements and fixes here and there.
> 
> Please let me know if there are problems!

Pulled, thanks John.

      reply	other threads:[~2011-03-12 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 21:06 pull request: wireless-next-2.6 2011-03-11 John W. Linville
2011-03-11 21:06 ` John W. Linville
2011-03-12 22:40 ` 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=20110312.144032.71127259.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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 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.