public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Daniel Lezcano <daniel.lezcano@linaro•org>,
	akpm@linux-foundation•org, rob.lee@linaro•org, j-pihet@ti•com,
	khilman@ti•com, deepthi@linux•vnet.ibm.com,
	dan.carpenter@oracle•com, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org, amit.kucheria@linaro•org
Subject: Re: [PATCH] cpuidle : fix random hangs with intel_idle
Date: Wed, 14 Mar 2012 17:23:26 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LSU.2.00.1203141720360.2003@eggly.anvils> (raw)
In-Reply-To: <20120315111415.cd119171ac86967aebe85545@canb.auug.org.au>

On Thu, 15 Mar 2012, Stephen Rothwell wrote:
> On Thu, 15 Mar 2012 01:09:41 +0100 Daniel Lezcano <daniel.lezcano@linaro•org> wrote:
> >
> > The cpuidle consolidation inverts the local_irq_enable for
> > the poll_idle function with CPU_RELAX.
> > 
> > Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro•org>
> > Reported-by: Hugh Dickins <hughd@google•com>
> 
> So this needs to go into Rob's tree.  Maybe after Hugh verifies that it
> fixes his problem.

Yes, Daniel got me to try it offline before he posted it.

Tested-by: Hugh Dickins <hughd@google•com>

Personally, I'd recommend including it even before it gets into Rob's
tree (where it may well be improved upon first): it does a lot to
improve the usability of linux-next.

Hugh

  reply	other threads:[~2012-03-15  0:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 22:29 next-20120313 cpuidle freezes when booting Hugh Dickins
2012-03-14 11:29 ` Daniel Lezcano
2012-03-14 19:03   ` Hugh Dickins
2012-03-14 19:46     ` Daniel Lezcano
2012-03-14 20:30       ` Hugh Dickins
2012-03-15  0:09 ` [PATCH] cpuidle : fix random hangs with intel_idle Daniel Lezcano
2012-03-15  0:14   ` Stephen Rothwell
2012-03-15  0:23     ` Hugh Dickins [this message]
2012-03-15  2:58       ` Stephen Rothwell
2012-03-16 13:37         ` Amit Kucheria
2012-03-16 14:26           ` Stephen Rothwell
2012-03-20 16:27             ` Rob Lee

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=alpine.LSU.2.00.1203141720360.2003@eggly.anvils \
    --to=hughd@google$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=amit.kucheria@linaro$(echo .)org \
    --cc=dan.carpenter@oracle$(echo .)com \
    --cc=daniel.lezcano@linaro$(echo .)org \
    --cc=deepthi@linux$(echo .)vnet.ibm.com \
    --cc=j-pihet@ti$(echo .)com \
    --cc=khilman@ti$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rob.lee@linaro$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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