Netdev List
 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 2012-10-01
Date: Mon, 01 Oct 2012 16:00:42 -0400 (EDT)	[thread overview]
Message-ID: <20121001.160042.2132360219816463227.davem@davemloft.net> (raw)
In-Reply-To: <20121001192448.GA1944@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Mon, 1 Oct 2012 15:24:49 -0400

> commit e4d680c706284ca0413a84bd2a28fda76b360904
> 
> In my previous pull request, I mentioned that I had a few stragglers.
> They are all driver updates: ti, brcmfmac, ath9k, one for bcma and
> one for b43legacy.  I merged them late last week and was letting them
> soak in linux-next.  I hope they can still make 3.7.
> 
> Please let me know if there are problems!

Pulled, thanks John.

      reply	other threads:[~2012-10-01 20:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 19:24 pull request: wireless-next 2012-10-01 John W. Linville
2012-10-01 20:00 ` 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=20121001.160042.2132360219816463227.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