public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Sergio Luis <sergio@larces.uece.br>
Cc: "Linux-kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Pavel Machek" <pavel@suse.cz>,
	"x86 Maintainers" <x86@kernel.org>, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: [PATCH 0/6] x86: unify power/cpu_(32|64).c
Date: Sat, 4 Apr 2009 23:12:45 +0200	[thread overview]
Message-ID: <200904042312.46429.rjw@sisk.pl> (raw)
In-Reply-To: <49D71E2B.5060501@larces.uece.br>

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

      reply	other threads:[~2009-04-04 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04  8:45 [PATCH 0/6] x86: unify power/cpu_(32|64).c Sergio Luis
2009-04-04 21:12 ` Rafael J. Wysocki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200904042312.46429.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@suse.cz \
    --cc=sergio@larces.uece.br \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox