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 2011-09-16
Date: Fri, 16 Sep 2011 15:20:50 -0400 (EDT) [thread overview]
Message-ID: <20110916.152050.74502091191784524.davem@davemloft.net> (raw)
In-Reply-To: <20110916183118.GB22612@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 16 Sep 2011 14:31:19 -0400
> This is a batch of updates intended for 3.2. They have been simmering
> for a while, since I merged them just before the big kernel.org
> shutdown. That includes time in wireless-testing and linux-next
> (albeit the latter is diminished by the kernel.org outage). For now,
> I am just trying to clear the backlog... :-)
>
> This includes a sizable wl12xx pull and a bunch of iwlagn updates.
> There are also a number of ath9k updates, some b43 updates, and a
> handful of other bits.
>
> Please let me know if there are problems!
Pulled, thanks John.
prev parent reply other threads:[~2011-09-16 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 18:31 pull request: wireless-next 2011-09-16 John W. Linville
2011-09-16 19:20 ` 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=20110916.152050.74502091191784524.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 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).