linux-kernel - Re: [linux-pm] 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 27 Jan 2008 00:42:38 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Len Brown <lenb@...nel.org>
Cc:	linux-pm@...ts.linux-foundation.org, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [linux-pm] Q: x86 suspend/hibernation code consolidation

On Saturday, 26 of January 2008, Len Brown wrote:
> On Friday 25 January 2008 19:32, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > 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.
> > 
> > When is the right time for making changes like that?
> > 
> > Rafael
> 
> In Cambridge, when we discussed cleanups that touch a lot of files
> but have no functional change -- somebody suggested that right
> after rc1 closes is a good time.  The reasoning was that they
> would not conflict with the functional changes in rc1.
> 
> However, I recall Linus saying something about "Andrew is special"
> WRT permission to push cleanups after the rc1 window; so I don't
> know what the final ruling was -- if there was such a ruling.

Well, I don't think there was a ruling, but perhaps sneaking it into -mm
after -rc1 would do the trick. ;-)

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/