On Wed, Feb 8, 2023 at 6:05 AM Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > > On 07-02-23, 20:59, Uwe Kleine-König wrote: > > All but a few drivers ignore the return value of > > cpufreq_unregister_driver(). Those few that don't only call it after > > cpufreq_register_driver() succeeded, in which case the call doesn't > > fail. > > > > Make the function return no value and add a WARN_ON for the case that > > the function is called in an invalid situation (i.e. without a previous > > successful call to cpufreq_register_driver()). > > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> > > --- > > drivers/cpufreq/brcmstb-avs-cpufreq.c | 5 +---- > > drivers/cpufreq/cpufreq.c | 8 +++----- > > drivers/cpufreq/davinci-cpufreq.c | 4 +++- > > drivers/cpufreq/mediatek-cpufreq-hw.c | 4 +++- > > drivers/cpufreq/omap-cpufreq.c | 4 +++- > > drivers/cpufreq/qcom-cpufreq-hw.c | 4 +++- > > include/linux/cpufreq.h | 2 +- > > 7 files changed, 17 insertions(+), 14 deletions(-) > > Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx> Applied as 6.3 material, thanks!
