linux-kernel - Re: Q: x86 suspend/hibernation code consolidation

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200801281601.41651.rjw@sisk.pl>
Date:	Mon, 28 Jan 2008 16:01:40 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Pavel Machek <pavel@....cz>,
	pm list <linux-pm@...ts.linux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Len Brown <lenb@...nel.org>
Subject: Re: Q: x86 suspend/hibernation code consolidation

On Monday, 28 of January 2008, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw@...k.pl> wrote:
> 
> > I'd like to move the 64-bit suspend/hibernation files from 
> > arch/x86/kernel to arch/x86/power, modify the names of the 32-bit 
> > files already in arch/x86/power and update the Makefiles accordingly, 
> > but there are some changes queued for merging that touch the files in 
> > question.
> 
> nice cleanup.
> 
> > When is the right time for making changes like that?
> 
> best would be after the x86.git merge. We could push this via x86.git in 
> fact, to line it up with whatever other changes there might be. -mm 
> would be fine too, if there are pending patches in this area in -mm.

There is one patch in acpi.git, AFAICS, so I guess I'd have to wait for both
x86.git and acpi.git with that, which means -rc1 time frame more or less.
 
> (and i recall you did some global-scope suspend/resume changes that 
> might interfere?)

Some of them are in acpi.git and some have been merged already.

Thanks,
Rafael
--
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/