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 2013-12-06
Date: Fri, 06 Dec 2013 14:45:26 -0500 (EST) [thread overview]
Message-ID: <20131206.144526.1713594401898800646.davem@davemloft.net> (raw)
In-Reply-To: <20131206184920.GG13285@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 6 Dec 2013 13:49:20 -0500
> Please pull this batch of updates intended for the 3.14 stream...
>
> For the mac80211 bits, Johannes says:
>
> "I have various improvements/cleanups/fixes all over, but the shortlog
> shows that Luis's regulatory work and mesh work from the cozybit folks
> are the biggest ones, along with the CSA fixes."
>
> Along with that, we have big batches of updates to brcmfmac, rtlwifi,
> and ath9k. There are updates to wcn36xx, rt2x00, and a handful of
> others as well.
>
> Please let me know if there are problems!
Pulled, thanks a lot John.
prev parent reply other threads:[~2013-12-06 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 18:49 pull request: wireless-next 2013-12-06 John W. Linville
2013-12-06 19:45 ` 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=20131206.144526.1713594401898800646.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).