netdev - Re: pull request: wireless-2.6 2008-11-06

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: <20081106.155954.52066801.davem@davemloft.net>
Date:	Thu, 06 Nov 2008 15:59:54 -0800 (PST)
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 2008-11-06

From: "John W. Linville" <linville@...driver.com>
Date: Thu, 6 Nov 2008 17:49:04 -0500

> Here is the latest round of wireless bits intended for 2.6.28.  It
> includes a revert of an earlier fix that greatly reduced interrupts
> handled by ath5k -- testing showed that it resulted in a greater number
> of dropped associations.
> 
> Also included is an iwlwifi patch ("iwlwifi: clear scanning bits upon
> failure") that is already in -next.  It does not seem to be a strict
> regression, but since it is simple and can leave the device unable to
> scan (i.e. effectively inoperative) I think it is worth having now.
> There are also iwl3945 versions of some iwlwifi fixes as well as an
> iwl3945-specific one related to firmware errors.
> 
> Further, there is a WARN_ON fix for ath5k and another iwlwifi fix from
> me to avoid a possible sleep in softirq context.  Just for fun I've
> thrown-in a couple of zd1211rw USB ID additions as well.

Pulled, thanks a lot John.

> Please let me know if there are problems!  Any mistakes I blame on my
> recent bout of pneumonia...

Hope you feel better soon.
--
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