linux-kernel - Re: [GIT pull request] ACPI patches for 2.6.34-rc3

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.2.00.1004061646170.4168@localhost.localdomain>
Date:	Tue, 06 Apr 2010 16:47:47 -0400 (EDT)
From:	Len Brown <lenb@...nel.org>
To:	Rafał Miłecki <zajec5@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-acpi@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT pull request] ACPI patches for 2.6.34-rc3


On Tue, 6 Apr 2010, Rafał Miłecki wrote:

> W dniu 6 kwietnia 2010 09:09 użytkownik Len Brown <lenb@...nel.org> napisał:
> > commit c8cf3a14a6615e06504664cd50ca90baa5f2ef7d
> > Author: Rafael Wysocki <rjw@...k.pl>
> > Date:   Thu Mar 4 00:25:30 2010 +0000
> >
> >    ACPI / PM: Move ACPI video resume to a PM notifier
> >
> >    There is a problem with the ACPI video resume routine that it's
> >    executed before the GPU that may be accessed by it.  To fix this
> >    issue, move the ACPI video resume to a power management notifier,
> >    so that it's executed after resuming all devices, including the GPU.
> >
> >    http://bugzilla.kernel.org/show_bug.cgi?id=15096
> >
> >    Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
> >    Acked-by: Matthew Garrett <mjg@...hat.com>
> >    Tested-by: Rafał Miłecki <zajec5@...il.com>
> >    Signed-off-by: Len Brown <len.brown@...el.com>
> 
> Could you push this one to stable as well, please? It partially fixes
> regression reported in:
> https://bugzilla.kernel.org/show_bug.cgi?id=15096
> 
> This should go to .32 and .33.

Yes, after it is upstream, it can be sent to .stable.
In this case it applies to .33, and will need some modification for .32
At that point, the bugzilla entry is closed.

cheers,
Len Brown, Intel Open Source Technology Center