netdev - Re: pull request: wireless 2011-09-20

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: <20110920.134705.385231251761546079.davem@davemloft.net>
Date:	Tue, 20 Sep 2011 13:47:05 -0400 (EDT)
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 2011-09-20

From: "John W. Linville" <linville@...driver.com>
Date: Tue, 20 Sep 2011 13:05:01 -0400

> This is a batch of fixes intended for 3.1.
> 
> Included is a set of Bluetooth fixes from Gustavo:
> 
> 	This is probably my unique pull request for 3.1, it fixes
> 	an regression with the HCI_INQUIRY flag, it was not getting
> 	cleaned after scan. Fix by Oliver Neukum. Also support for
> 	two new apple devices and a simple fix the to btwilink driver.
> 
> Also included is an iwlagn patch revert to avoid some AP crashes, an
> rt2800 patch to refactor some code that triggers a compiler bug, another
> rt2800 patch to correct an endian bug, a b43 fix to restore beaconing in
> ad-hoc mode, a regulatory enforcement fix for a problem that prevented
> multiple regulatory domain changes from beacons, a fix to use the proper
> rates in a probe request, and a fix for a deadlock that had crept into
> ipw2200 after an earlier patch.
> 
> Please let me know if there are problems!

Pulled, but this is very nearly "too much" this late in the game.

I recognize the issue that we've been stuck in a state of pseudo-limbo
up until a couple days ago, so I took this.
--
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