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-02-08
Date: Tue, 08 Feb 2011 13:53:27 -0800 (PST) [thread overview]
Message-ID: <20110208.135327.115933299.davem@davemloft.net> (raw)
In-Reply-To: <20110208204139.GC6244@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Tue, 8 Feb 2011 15:41:39 -0500
> Here is the latest round of wireless bits intended for 2.6.39.
> This is mostly driver updates (as usual), including a flurry of
> wl1251 patches from David Gnedt. ath5k, ath9k, and iwlwifi are
> well represented, of course. Interestingly, this batch includes a
> number of mac80211 patches -- most of them _not_ from Johannes Berg!
> I doubt if that holds for long... :-) And, zd1211rw grows AP support.
> Also, this includes a wireless-2.6 pull to resolve some merge conflicts.
>
> Please let me know if there are problems!
Pulled, thanks a lot John.
prev parent reply other threads:[~2011-02-08 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 20:41 pull request: wireless-next-2.6 2011-02-08 John W. Linville
2011-02-08 21:53 ` 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=20110208.135327.115933299.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).