[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5243586A.1090605@linaro.org>
Date: Wed, 25 Sep 2013 23:40:58 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Viresh Kumar <viresh.kumar@...aro.org>, rjw@...k.pl
CC: linaro-kernel@...ts.linaro.org, patches@...aro.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 06/21] cpuidle: rearrange code in __cpuidle_driver_init()
On 09/22/2013 03:20 AM, Viresh Kumar wrote:
> This is trivial patch that just reorders few statements in
> __cpuidle_driver_init() routine, so that we don't need both 'continue' and
> 'break' in the for loop. Functionally it shouldn't change anything.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---
> drivers/cpuidle/driver.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c
> index 8df66c8..6279e1c 100644
> --- a/drivers/cpuidle/driver.c
> +++ b/drivers/cpuidle/driver.c
> @@ -172,12 +172,10 @@ static void __cpuidle_driver_init(struct cpuidle_driver *drv)
> * order, because usually one of the deeper states have this flag set.
> */
> for (i = drv->state_count - 1; i >= 0 ; i--) {
> -
> - if (!(drv->states[i].flags & CPUIDLE_FLAG_TIMER_STOP))
> - continue;
> -
> - drv->bctimer = 1;
> - break;
> + if (drv->states[i].flags & CPUIDLE_FLAG_TIMER_STOP) {
> + drv->bctimer = 1;
> + break;
> + }
> }
> }
Well, I don't have a strong opinion on that, it is "Schtroumpf Vert et
Vert Schtroumpf" :) [1]
-- Daniel
[1] http://en.wikipedia.org/wiki/Schtroumpf_Vert_et_Vert_Schtroumpf
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
--
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