From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Amit Kucheria <amitk@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Yang Yingliang <yangyingliang@huawei.com>,
Zhang Rui <rui.zhang@intel.com>
Cc: linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Caleb Connolly <caleb.connolly@linaro.org>,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: [PATCH 0/3] thermal: Fix/cleanup error paths in __thermal_cooling_device_register()
Date: Wed, 18 Jan 2023 14:08:23 +0530 [thread overview]
Message-ID: <cover.1674030722.git.viresh.kumar@linaro.org> (raw)
Hi,
The error paths in __thermal_cooling_device_register() are trying to free
un-acquired resources, fix that and clean it up a bit.
Caleb, can you please test this? I have just build tested it for now.
--
Viresh
Viresh Kumar (3):
thermal: core: call put_device() only after device_register() fails
thermal: core: Move cdev cleanup to thermal_release()
thermal: core: Use device_unregister() instead of device_del/put()
drivers/thermal/thermal_core.c | 29 +++++++++++++++--------------
1 file changed, 15 insertions(+), 14 deletions(-)
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2023-01-18 9:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 8:38 Viresh Kumar [this message]
2023-01-18 8:38 ` [PATCH V4 1/3] thermal: core: call put_device() only after device_register() fails Viresh Kumar
2023-01-18 19:57 ` Frank Rowand
2023-01-18 19:58 ` Rafael J. Wysocki
2023-01-19 5:16 ` Viresh Kumar
2023-01-19 20:09 ` Rafael J. Wysocki
2023-01-24 19:26 ` Rafael J. Wysocki
2023-01-19 8:13 ` Yang Yingliang
2023-01-19 15:02 ` Caleb Connolly
2023-01-18 8:38 ` [PATCH 2/3] thermal: core: Move cdev cleanup to thermal_release() Viresh Kumar
2023-01-19 8:25 ` Yang Yingliang
2023-01-18 8:38 ` [PATCH 3/3] thermal: core: Use device_unregister() instead of device_del/put() Viresh Kumar
2023-01-19 8:25 ` Yang Yingliang
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=cover.1674030722.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=amitk@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=vincent.guittot@linaro.org \
--cc=yangyingliang@huawei.com \
/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).