From: Viresh Kumar <viresh.kumar@linaro.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: linux-kernel@vger.kernel.org, edubezval@gmail.com,
Amit Daniel Kachhap <amit.kachhap@gmail.com>,
Amit Kucheria <amit.kucheria@verdurent.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Guillaume La Roque <glaroque@baylibre.com>,
Heiko Stuebner <heiko@sntech.de>,
Javi Merino <javi.merino@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Jun Nie <jun.nie@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Kukjin Kim <kgene@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Zhang Rui <rui.zhang@intel.com>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 04/11] thermal: devfreq_cooling: Appease the kernel-doc deity
Date: Thu, 21 Nov 2019 11:01:00 +0530 [thread overview]
Message-ID: <20191121053100.n3vfo564gs2sn72v@vireshk-i7> (raw)
In-Reply-To: <7059d82472fe12139fc7a3379c5b9716a23cce5c.1574242756.git.amit.kucheria@linaro.org>
On 20-11-19, 21:15, Amit Kucheria wrote:
> Fix up the following warnings with make W=1:
>
> linux.git/drivers/thermal/devfreq_cooling.c:68: warning: Function
> parameter or member 'capped_state' not described in
> 'devfreq_cooling_device'
> linux.git/drivers/thermal/devfreq_cooling.c:593: warning: Function
> parameter or member 'cdev' not described in 'devfreq_cooling_unregister'
> linux.git/drivers/thermal/devfreq_cooling.c:593: warning: Excess
> function parameter 'dfc' description in 'devfreq_cooling_unregister'
>
> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org>
> ---
> drivers/thermal/devfreq_cooling.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2019-11-21 5:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 15:45 [PATCH v2 00/11] thermal: clean up output of make W=1 Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 01/11] thermal: of-thermal: Appease the kernel-doc deity Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 02/11] thermal: cpu_cooling: " Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 03/11] thermal: step_wise: " Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 04/11] thermal: devfreq_cooling: " Amit Kucheria
2019-11-21 5:31 ` Viresh Kumar [this message]
2019-11-20 15:45 ` [PATCH v2 05/11] thermal: max77620: " Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 06/11] thermal: mediatek: " Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 07/11] thermal: rockchip: " Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 08/11] thermal: samsung: " Amit Kucheria
2019-11-21 5:32 ` Viresh Kumar
2019-11-20 15:45 ` [PATCH v2 09/11] thermal: tegra: " Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 10/11] thermal: amlogic: " Amit Kucheria
2019-11-20 15:45 ` [PATCH v2 11/11] thermal: zx2967: " Amit Kucheria
2019-12-04 16:29 ` [PATCH v2 00/11] thermal: clean up output of make W=1 Daniel Lezcano
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=20191121053100.n3vfo564gs2sn72v@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=amit.kachhap@gmail.com \
--cc=amit.kucheria@linaro.org \
--cc=amit.kucheria@verdurent.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=glaroque@baylibre.com \
--cc=heiko@sntech.de \
--cc=javi.merino@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=jun.nie@linaro.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rui.zhang@intel.com \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@gmail.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).