From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Leo Yan <leo.yan@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ARM: cpuidle: Refactor rollback operations if init fails
Date: Wed, 11 Oct 2017 11:49:16 +0200 [thread overview]
Message-ID: <2c39f935-9fd1-fb96-d6db-c9dd92e2d833@linaro.org> (raw)
In-Reply-To: <1507614476-16054-2-git-send-email-leo.yan@linaro.org>
On 10/10/2017 07:47, Leo Yan wrote:
> If init fails, we need execute two levels rollback operations: the first
> level is for the failed CPU rollback operations, the second level is to
> iterate all succeeded CPUs to cancel their registration; currently the
> code uses one function to finish these two levels rollback operations.
>
> This commit is to refactor rollback operations, so it adds a new
> function arm_idle_init_cpu() to encapsulate one specified CPU driver
> registration and rollback the first level operations; and use function
> arm_idle_init() to iterate all CPUs and finish the second level's
> rollback operations.
>
> Suggested-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<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
next prev parent reply other threads:[~2017-10-11 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 5:47 [PATCH v2 1/2] ARM: cpuidle: Correct driver unregistration if init fails Leo Yan
2017-10-10 5:47 ` [PATCH v2 2/2] ARM: cpuidle: Refactor rollback operations " Leo Yan
2017-10-11 9:49 ` Daniel Lezcano [this message]
2017-10-10 22:00 ` [PATCH v2 1/2] ARM: cpuidle: Correct driver unregistration " Rafael J. Wysocki
2017-10-11 9:48 ` Daniel Lezcano
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=2c39f935-9fd1-fb96-d6db-c9dd92e2d833@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).