linux-kernel - Re: pull request: wireless-2.6 2009-11-11

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Nov 2009 11:20:31 -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 2009-11-11

From: "John W. Linville" <linville@...driver.com>
Date: Wed, 11 Nov 2009 12:22:55 -0500

> Here is another batch of small fixes intended for 2.6.32.  Along with a
> number of simple fixes, there is also a MAINTAINERS update, some LED
> handling quirks for ath5k, a libertas beautification that is a prereq
> for a libertas fix, and an iwlwifi fix that was already sent for
> net-next-2.6 but which is needed to support an iwlwifi regression fix.
> 
> My personal favorite is the ath5k mcast filtering fix.  The problem
> only revealed itself when using IP autoconf w/ multicast DNS... :-)
> 
> Please let me know if there are problems!

Pulled, but that libertas "coding style cleanup" really pushes
the edge of what I'm willing to take into net-2.6 right now.

And I don't want to hear anything about how it "makes the bug fix
change simpler".  That absolutely doesn't apply when we're this deep
in -rc territory.

> P.S.  Due to the aformentioned iwlwifi fix, this will cause -next
> conflicts for sfr.  You may want to pull net-2.6 into net-next-2.6 after
> pulling this.  The iwlwifi conflicts can be resolved by taking the bigger
> hunks...

Yep, I noticed this, I'll sort it out, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/