From: Viresh Kumar <viresh.kumar@linaro.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
daniel.lezcano@linaro.org, sudeep.holla@arm.com,
bjorn.andersson@linaro.org, edubezval@gmail.com,
agross@kernel.org, tdas@codeaurora.org, swboyd@chromium.org,
ilina@codeaurora.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Amit Kucheria <amit.kucheria@verdurent.com>,
Zhang Rui <rui.zhang@intel.com>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 2/6] thermal: Initialize thermal subsystem earlier
Date: Fri, 18 Oct 2019 11:36:00 +0530 [thread overview]
Message-ID: <20191018060600.oj2qf5tuqu5agfmb@vireshk-i7> (raw)
In-Reply-To: <cc2aa18e2e6004ba099e69b41d0d505a4361443c.1571314830.git.amit.kucheria@linaro.org>
On 17-10-19, 17:57, Amit Kucheria wrote:
> Now that the thermal framework is built-in, in order to facilitate
> thermal mitigation as early as possible in the boot cycle, move the
> thermal framework initialization to core_initcall.
>
> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org>
> ---
> drivers/thermal/thermal_core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
> index d21b754baee2..d8251d723459 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -1537,4 +1537,5 @@ static int __init thermal_init(void)
> mutex_destroy(&poweroff_lock);
> return result;
> }
> -fs_initcall(thermal_init);
> +
remove the blank line please.
> +core_initcall(thermal_init);
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2019-10-18 6:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 12:27 [PATCH v3 0/6] Initialise thermal framework and cpufreq earlier during boot Amit Kucheria
2019-10-17 12:27 ` [PATCH v3 1/6] thermal: Remove netlink support Amit Kucheria
2019-10-18 6:05 ` Viresh Kumar
2019-10-17 12:27 ` [PATCH v3 2/6] thermal: Initialize thermal subsystem earlier Amit Kucheria
2019-10-18 6:06 ` Viresh Kumar [this message]
2019-10-17 12:27 ` [PATCH v3 3/6] cpufreq: Initialise the governors in core_initcall Amit Kucheria
2019-10-17 19:11 ` Rafael J. Wysocki
2019-10-17 19:42 ` Amit Kucheria
2019-10-17 12:27 ` [PATCH v3 4/6] cpufreq: Initialize cpufreq-dt driver earlier Amit Kucheria
2019-10-17 12:27 ` [PATCH v3 5/6] clk: qcom: Initialise clock drivers earlier Amit Kucheria
2019-10-17 17:47 ` Stephen Boyd
2019-10-18 6:03 ` Viresh Kumar
[not found] ` <20191028172225.1B1CF20862@mail.kernel.org>
2019-10-29 1:06 ` Sudeep Holla
2019-11-05 6:50 ` Viresh Kumar
2019-10-17 12:27 ` [PATCH v3 6/6] cpufreq: qcom-hw: Move driver initialisation earlier Amit Kucheria
2019-10-17 18:19 ` Taniya Das
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=20191018060600.oj2qf5tuqu5agfmb@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=agross@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=amit.kucheria@verdurent.com \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=sudeep.holla@arm.com \
--cc=swboyd@chromium.org \
--cc=tdas@codeaurora.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 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).