linux-kernel - Re: bcm43xx regression in 2.6.24 (with patch)

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]

Message-ID: <Pine.LNX.4.64.0802251423190.21696@sbz-30.cs.Helsinki.FI>
Date:	Mon, 25 Feb 2008 14:25:38 +0200 (EET)
From:	Pekka J Enberg <penberg@...helsinki.fi>
To:	Michael Buesch <mb@...sch.de>
cc:	Greg KH <greg@...ah.com>,
	Alexey Zaytsev <alexey.zaytsev@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Alexey Zaytsev <zaytsev.a@...tei.ru>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: bcm43xx regression in 2.6.24 (with patch)

On Mon, 25 Feb 2008, Michael Buesch wrote:
> > Neither of which seem like acceptable solutions for a 2.6.23 -> 2.6.24
> > _regression_. Or maybe I am just too naive to believe Linus' statement
> > on not letting the kernel regress...
> 
> So, please sign-off the patch that we have, if you think it's right
> and doesn't cause more regressions.

I did look at the patch and can gladly add a:

Reviewed-by: Pekka Enberg <penberg@...helsinki.fi>

But this seems backwards. It was _your_ commit that broke the setup and 
the patch touches a driver _you're_ maintaining.

So can we just revert commit 753f492093da7a40141bfe083073400f518f4c68 
("[B44]: port to native ssb support") from 2.6.24 and you can add it back 
to 2.6.25 if the problem indeed does go away?

			Pekka
--
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/