[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090408123413.GF18581@elte.hu>
Date: Wed, 8 Apr 2009 14:34:13 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Pavel Machek <pavel@....cz>, Sergio Luis <sergio@...ces.uece.br>,
Linux-kernel Mailing List <linux-kernel@...r.kernel.org>,
Lauro Salmito <laurosalmito@...il.com>,
x86 Maintainers <x86@...nel.org>
Subject: Re: [PATCH 6/6] x86: unify power/cpu_(32|64).c
* Rafael J. Wysocki <rjw@...k.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@...ces.uece.br>
> > > Signed-off-by: Lauro Salmito <laurosalmito@...il.com>
> >
> >
> > Whole series looks ok to me.
> >
> > Acked-by: Pavel Machek <pavel@....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
--
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/
Powered by blists - more mailing lists