public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>, Sergio Luis <sergio@larces.uece.br>,
	Linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lauro Salmito <laurosalmito@gmail.com>,
	x86 Maintainers <x86@kernel.org>
Subject: Re: [PATCH 6/6] x86: unify power/cpu_(32|64).c
Date: Wed, 8 Apr 2009 14:34:13 +0200	[thread overview]
Message-ID: <20090408123413.GF18581@elte.hu> (raw)
In-Reply-To: <200904042304.25088.rjw@sisk.pl>


* Rafael J. Wysocki <rjw@sisk.pl> wrote:

> On Monday 30 March 2009, Pavel Machek wrote:
> > Hi!
> > 
> > > x86: unify power/cpu_(32|64).c
> > > 
> > > This is the last unification step. Here we do remove one of the files
> > > and rename the left one as cpu.c, as both are now the same.
> > > Also update power/Makefile, telling it to build cpu.o, instead of
> > > cpu_(32|64).o
> > > 
> > > Signed-off-by: Sergio Luis <sergio@larces.uece.br>
> > > Signed-off-by: Lauro Salmito <laurosalmito@gmail.com>
> > 
> > 
> > Whole series looks ok to me.
> > 
> > Acked-by: Pavel Machek <pavel@ucw.cz>
> 
> However, there's no way it can go in before 2.6.30 final.

Correct.

> I'm reviewing it at the moment.

Feel free to queue these bits up in your tree - it's largely related 
to your area anyway. That way you can stage it in the most robust 
way. You have a stable (append-only) Git tree for suspend/resume 
bits, which propagates into linux-next, correct?

	Ingo

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04  8:48 [PATCH 6/6] x86: unify power/cpu_(32|64).c Sergio Luis
2009-03-30 10:25 ` Pavel Machek
2009-04-04 21:04   ` Rafael J. Wysocki
2009-04-08 12:34     ` Ingo Molnar [this message]
2009-04-08 21:10       ` Rafael J. Wysocki

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=20090408123413.GF18581@elte.hu \
    --to=mingo@elte.hu \
    --cc=laurosalmito@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --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