From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: rjw@rjwysocki.net, nicolas.pitre@linaro.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 3/5] cpuidle: idle: menu: Don't reflect when a state selection failed
Date: Fri, 24 Oct 2014 15:24:28 +0200 [thread overview]
Message-ID: <20141024132428.GJ12706@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <1413822343-1972-3-git-send-email-daniel.lezcano@linaro.org>
On Mon, Oct 20, 2014 at 06:25:41PM +0200, Daniel Lezcano wrote:
> - if (index > 0)
> - if (index >= 0)
That's not the same condition.
next prev parent reply other threads:[~2014-10-24 13:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 16:25 [PATCH 1/5] sched: idle: cpuidle: Check the latency req before idle Daniel Lezcano
2014-10-20 16:25 ` [PATCH 2/5] sched: idle: Get the next timer event and pass it the cpuidle framework Daniel Lezcano
2014-10-22 20:38 ` Nicolas Pitre
2014-10-28 1:53 ` Len Brown
2014-10-28 6:40 ` Preeti Murthy
2014-10-28 18:02 ` Daniel Lezcano
2014-10-20 16:25 ` [PATCH 3/5] cpuidle: idle: menu: Don't reflect when a state selection failed Daniel Lezcano
2014-10-22 20:41 ` Nicolas Pitre
2014-10-24 13:24 ` Peter Zijlstra [this message]
2014-10-24 13:32 ` Daniel Lezcano
2014-10-24 13:38 ` Peter Zijlstra
2014-10-24 13:43 ` Daniel Lezcano
2014-10-24 13:56 ` Peter Zijlstra
2014-10-20 16:25 ` [PATCH 4/5] cpuidle: menu: Fix the get_typical_interval Daniel Lezcano
2014-10-20 16:25 ` [PATCH 5/5] cpuidle: menu: Move the update function before its declaration Daniel Lezcano
2014-10-22 20:30 ` [PATCH 1/5] sched: idle: cpuidle: Check the latency req before idle Nicolas Pitre
2014-10-27 22:58 ` Rafael J. Wysocki
2014-10-28 8:30 ` Peter Zijlstra
2014-10-28 1:49 ` Len Brown
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=20141024132428.GJ12706@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.lezcano@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.