diff options
author | Leonard Crestez <leonard.crestez@nxp.com> | 2019-11-14 02:21:31 +0300 |
---|---|---|
committer | Chanwoo Choi <cw00.choi@samsung.com> | 2019-12-09 06:19:16 +0300 |
commit | 42a6b25e67df6ee6675e8d1eaf18065bd73328ba (patch) | |
tree | 93ef7484ead19ba4f60bb7f1b7ebe8a7030a6478 /scripts | |
parent | 46cecc0bf095bbffdf58618a1b4a5f9c9f073bf8 (diff) | |
download | linux-42a6b25e67df6ee6675e8d1eaf18065bd73328ba.tar.xz |
PM / devfreq: Don't fail devfreq_dev_release if not in list
Right now devfreq_dev_release will print a warning and abort the rest of
the cleanup if the devfreq instance is not part of the global
devfreq_list. But this is a valid scenario, for example it can happen if
the governor can't be found or on any other init error that happens
after device_register.
Initialize devfreq->node to an empty list head in devfreq_add_device so
that list_del becomes a safe noop inside devfreq_dev_release and we can
continue the rest of the cleanup.
Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions