From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next 2011-11-17
Date: Thu, 17 Nov 2011 14:34:45 -0500 (EST) [thread overview]
Message-ID: <20111117.143445.52753444311198143.davem@davemloft.net> (raw)
In-Reply-To: <20111117182939.GD32622-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Date: Thu, 17 Nov 2011 13:29:39 -0500
> Here is a huge pull request for wireless bits intended for 3.3. I
> reckon that the extended release cycle for 3.1 led to a backlog of new
> work that appeared during the merge window for 3.2?
>
> At any rate...there is a big Bluetooth pull with a lot of code
> refactoring; a lot of brcm80211 bits including cleanups, refactoring,
> and some new hardware support; the normal set of iwlwifi updates plus
> some refactoring; an unusual large flurry of mac80211 and cfg80211
> updates from Johannes (including the new wireless TX status socket
> option); some updates to the new NFC subsystem; and the usual collection
> of other driver and mac80211 updates. This also includes a pull of the
> wireless.git tree to resolve some build issues.
Pulled, thanks John.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-11-17 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 18:29 pull request: wireless-next 2011-11-17 John W. Linville
[not found] ` <20111117182939.GD32622-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2011-11-17 19:34 ` 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=20111117.143445.52753444311198143.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).