[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200715024951.zr36iuagany5ii56@vireshk-i7>
Date: Wed, 15 Jul 2020 08:19:51 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Lee Jones <lee.jones@...aro.org>
Cc: rjw@...ysocki.net, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
Dominik Brodowski <linux@...do.de>,
Ashok Raj <ashok.raj@...el.com>,
Jacob Shin <jacob.shin@....com>
Subject: Re: [PATCH 02/13] cpufreq: cpufreq: Demote lots of function headers
unworthy of kerneldoc status
On 14-07-20, 15:50, Lee Jones wrote:
> -/**
> +/*
> * cpufreq_remove_dev - remove a CPU device
Because cpufreq_add_dev() is part of kernel doc, we better keep it.
> *
> * Removes the cpufreq interface for a CPU device.
> @@ -2373,6 +2374,7 @@ EXPORT_SYMBOL_GPL(cpufreq_unregister_governor);
> * cpufreq_get_policy - get the current cpufreq_policy
> * @policy: struct cpufreq_policy into which the current cpufreq_policy
> * is written
> + * @cpu: CPU to find the policy for
> *
> * Reads the current cpufreq policy.
> */
> @@ -2759,7 +2761,7 @@ int cpufreq_register_driver(struct cpufreq_driver *driver_data)
> }
> EXPORT_SYMBOL_GPL(cpufreq_register_driver);
>
> -/**
> +/*
> * cpufreq_unregister_driver - unregister the current CPUFreq driver
And this should be there for sure.
> *
> * Unregister the current CPUFreq driver. Only call this if you have
> --
> 2.25.1
--
viresh
Powered by blists - more mailing lists