netdev - Re: pull request: wireless-2.6 2011-04-01

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20110401.171729.112600173.davem@davemloft.net>
Date:	Fri, 01 Apr 2011 17:17:29 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: pull request: wireless-2.6 2011-04-01

From: "John W. Linville" <linville@...driver.com>
Date: Fri, 1 Apr 2011 10:12:26 -0400

> On the Bluetooth front, we have a WARNING fix related to debugobjects, a
> fix for L2CAP channel hang, a fix for an unlock without a lock, a fix to
> check for LE connections before discarding data, a fix for
> synchronization after HCI_RESET, an accounting fix for unacked frames,
> and a device ID addition.
> 
> For wireless LANs, an iwlegacy fix to prevent a possible crash during a
> firmware restart, a carl9170 fix to generate BlockAckReq if the
> transmission of an AMPDU subframe fails (i.e. an interop fix), an
> iwl3945 change to disable hw scan by default due to a number of related
> problems, a related debug message change to avoid some confusion, a fix
> for aggregation frame reordering, a cfg80211 fix to avoid
> double-unlinking a BSS entry, a trio of NULL pointer deref fixes, an
> ath9k fix to avoid a bus error during restart, a minstrel_ht fix to
> avoid a crash when no supported MCS rates are found, and some new device
> IDs for rt2x00.
> 
> Please let me know if there are problems!

Looks good, 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