From: Kevin Hilman <khilman@baylibre.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Lina Iyer <lina.iyer@linaro.org>,
Jon Hunter <jonathanh@nvidia.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [RESEND PATCH 1/2] PM / Domains: Rename functions in genpd for power on/off
Date: Fri, 13 Jan 2017 11:53:58 -0800 [thread overview]
Message-ID: <m260li68ix.fsf@baylibre.com> (raw)
In-Reply-To: <1484241463-28435-2-git-send-email-ulf.hansson@linaro.org> (Ulf Hansson's message of "Thu, 12 Jan 2017 18:17:42 +0100")
Ulf Hansson <ulf.hansson@linaro.org> writes:
> Currently the mix of genpd_poweron(), genpd_power_on(),
> genpd_sync_poweron() and the ->power_on() callback, makes a bit difficult
> to follow the path of execution. The similar applies to the functions
> dealing with power off.
>
> In a way to improve this understanding, let's do the following renaming:
>
> genpd_power_on() -> _genpd_power_on()
> genpd_poweron() -> genpd_power_on()
> genpd_sync_poweron() -> genpd_sync_power_on()
>
> genpd_power_off() -> _genpd_power_off()
> genpd_poweroff() -> genpd_power_off()
> genpd_sync_poweroff() -> genpd_sync_power_off()
> genpd_poweroff_unused() -> genpd_power_off_unused()
>
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Acked-by: Kevin Hilman <khilman@baylibre.com>
next prev parent reply other threads:[~2017-01-13 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 17:17 [RESEND PATCH 0/2] PM / Domains: Fix asynchronous execution of *noirq() callbacks Ulf Hansson
2017-01-12 17:17 ` [RESEND PATCH 1/2] PM / Domains: Rename functions in genpd for power on/off Ulf Hansson
2017-01-13 19:53 ` Kevin Hilman [this message]
2017-01-12 17:17 ` [RESEND PATCH 2/2] PM / Domains: Fix asynchronous execution of *noirq() callbacks Ulf Hansson
2017-02-07 13:23 ` Geert Uytterhoeven
2017-02-07 15:07 ` Ulf Hansson
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=m260li68ix.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=briannorris@chromium.org \
--cc=geert@linux-m68k.org \
--cc=jonathanh@nvidia.com \
--cc=len.brown@intel.com \
--cc=lina.iyer@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.org \
/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.