linux-kernel - Re: Suspend to RAM regression (bisected)

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: <alpine.LFD.1.10.0807202119240.31863@woody.linux-foundation.org>
Date:	Sun, 20 Jul 2008 21:21:06 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Carlos R. Mafra" <crmafra2@...il.com>
cc:	linux-kernel@...r.kernel.org, airlied@...hat.com
Subject: Re: Suspend to RAM regression (bisected)

On Sun, 20 Jul 2008, Carlos R. Mafra wrote:
> 
> I bisected this regression down to c0e09200dc0813972442e550a5905a132768e56c
> ("drm: reorganise drm tree to be more future proof"), and I checked that
> reverting this commit (it reverts cleanly) really makes the regression go
> away.

Hmm. That did almost only just renames, so maybe it's fixed by the pull I 
just did that added the commit "gpu: re-order GPU subdirectory vs char for 
AGP vs DRM startup".

I _just_ pushed out the end result, so it should be in my git tree in a 
couple of minutes when the mirroring finishes.

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