linux-kernel - Re: [PATCH 0/6] x86: unify power/cpu

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] [day] [month] [year] [list]

Date:	Sat, 4 Apr 2009 23:12:45 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Sergio Luis <sergio@...ces.uece.br>
Cc:	"Linux-kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Pavel Machek" <pavel@...e.cz>, "x86 Maintainers" <x86@...nel.org>,
	"Ingo Molnar" <mingo@...e.hu>
Subject: Re: [PATCH 0/6] x86: unify power/cpu_(32|64).c

On Saturday 04 April 2009, Sergio Luis wrote:
> This patch series intends to unify the cpu_32.c and cpu_64.c files.
> 
> It's divided into 6 patches, that deal with the following:
> #1 - unify headers
> #2 - unify global variables
> #3 - unify saving of processor state
> #4 - unify restoring of processor state
> #5 - unify copyright notes on the files
> #6 - unify the files themselves, leaving only cpu.c
> 
> The code generated is _exactly_ the same as before, on both  i386 and
> x86-64 architectures, so I don't expect this to introduce _any_ new bugs.
> However, cleanups can be done in future, as for instance, the removal
> of a few global variables in the 32 bit architecture. We are not dealing 
> with those in this series.
> 
> The patches are against 2.6.29.

OK, you can add my ACK to the whole series.

Still, I wouldn't like it to go in before 2.6.30 final, because there are
enough deep changes related to suspend and resume already in the
Linus' tree.

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/