[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1426395191.2990.16.camel@gmail.com>
Date: Sun, 15 Mar 2015 05:53:11 +0100
From: Mike Galbraith <umgwanakikbuti@...il.com>
To: Ian Malone <ibmalone@...il.com>
Cc: Andy Lutomirski <luto@...capital.net>, Len Brown <lenb@...nel.org>,
x86@...nel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, Len Brown <len.brown@...el.com>,
Josh Boyer <jwboyer@...hat.com>, stable@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH REGRESSION FIX] x86 idle: restore mwait_idle()
On Sat, 2015-03-14 at 23:44 +0000, Ian Malone wrote:
> On 18 January 2014 at 16:14, Mike Galbraith <bitbucket@...ine.de> wrote:
> > On Sat, 2014-01-18 at 10:33 +0100, Mike Galbraith wrote:
> >> On Fri, 2014-01-17 at 05:20 +0100, Mike Galbraith wrote:
>
> > Signed-off-by: Mike Galbraith <bitbucket@...ine.de>
> > Cc: <stable@...r.kernel.org> # 3.10+
> > ---
> > arch/x86/kernel/process.c | 9 ++++++---
> > 1 file changed, 6 insertions(+), 3 deletions(-)
> >
> > --- a/arch/x86/kernel/process.c
> > +++ b/arch/x86/kernel/process.c
> > @@ -427,18 +427,21 @@ static int prefer_mwait_c1_over_halt(con
>
> Hi, this series of patches never seem to have made it as far as the
> mainline kernel, anyone know what needs to happen next?
My plan is to keep on carrying it locally for as long as I run new
kernels on crusty ole core2 boxen, then stop caring about them entirely
like the rest of the planet :)
-Mike
--
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