netdev - Re: pull request: wireless-next 2012-06-19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20120619.143838.2195312578230933662.davem@davemloft.net>
Date:	Tue, 19 Jun 2012 14:38:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: pull request: wireless-next 2012-06-19

From: "John W. Linville" <linville@...driver.com>
Date: Tue, 19 Jun 2012 15:57:57 -0400

> This is a sizeable batch of updates intended for 3.6...
> 
> The bulk of the changes here are Bluetooth.  Gustavo says:
> 
> 	Here goes the first Bluetooth pull request for 3.6, we have
> 	queued quite a lot of work. Andrei Emeltchenko added the AMP
> 	Manager code, a lot of work is needed, but the first bit are
> 	already there. This code is disabled by default.  Mat Martineau
> 	changed the whole L2CAP ERTM state machine code, replacing
> 	the old one with a new implementation. Besides that we had
> 	lot of coding style fixes (to follow net rules), more l2cap
> 	core separation from socket and many clean ups and fixed all
> 	over the tree.
> 
> Along with the above, there is a healthy dose of ath9k, iwlwifi,
> and other driver updates.  There is also another pull from the
> wireless tree to resolve some merge issues.  I also fixed-up some
> merge discrepencies between net-next and wireless-next.
> 
> Please let me know if there are problems!

Pulled, thanks JOhn.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html