From: Chanwoo Choi <cw00.choi@samsung.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH] devfreq: fix multiple kernel-doc warnings
Date: Mon, 9 Dec 2019 13:43:58 +0900 [thread overview]
Message-ID: <d4ce2bc5-4a07-f4e8-dffc-ec8a2c120edb@samsung.com> (raw)
In-Reply-To: <50975461-6dab-8f89-e802-b34ca06008f5@infradead.org>
Hi,
Thanks. But, You need to rebase it on updated devfreq-next or linux-next
after today. Because, when I applied it to updated devfreq-next
after released v5.5-rc1, the merge conflict happen.
Please rebase and resend it.
Regards,
Chanwoo Choi
On 12/9/19 1:34 PM, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix kernel-doc warnings in devfreq files.
> Also fix a typo.
>
> ../include/linux/devfreq.h:181: warning: Function parameter or member 'last_status' not described in 'devfreq'
>
> ../drivers/devfreq/devfreq.c:1687: warning: bad line: - Resource-managed devfreq_register_notifier()
> ../drivers/devfreq/devfreq.c:1723: warning: bad line: - Resource-managed devfreq_unregister_notifier()
> ../drivers/devfreq/devfreq-event.c:355: warning: Function parameter or member 'edev' not described in 'devfreq_event_remove_edev'
> ../drivers/devfreq/devfreq-event.c:355: warning: Excess function parameter 'dev' description in 'devfreq_event_remove_edev'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> Cc: Chanwoo Choi <cw00.choi@samsung.com>
> Cc: linux-pm@vger.kernel.org
> ---
> drivers/devfreq/devfreq-event.c | 4 ++--
> drivers/devfreq/devfreq.c | 4 ++--
> include/linux/devfreq.h | 3 ++-
> 3 files changed, 6 insertions(+), 5 deletions(-)
>
> --- linux-next-20191209.orig/drivers/devfreq/devfreq.c
> +++ linux-next-20191209/drivers/devfreq/devfreq.c
> @@ -1733,7 +1733,7 @@ static void devm_devfreq_notifier_releas
>
> /**
> * devm_devfreq_register_notifier()
> - - Resource-managed devfreq_register_notifier()
> + * - Resource-managed devfreq_register_notifier()
> * @dev: The devfreq user device. (parent of devfreq)
> * @devfreq: The devfreq object.
> * @nb: The notifier block to be unregistered.
> @@ -1769,7 +1769,7 @@ EXPORT_SYMBOL(devm_devfreq_register_noti
>
> /**
> * devm_devfreq_unregister_notifier()
> - - Resource-managed devfreq_unregister_notifier()
> + * - Resource-managed devfreq_unregister_notifier()
> * @dev: The devfreq user device. (parent of devfreq)
> * @devfreq: The devfreq object.
> * @nb: The notifier block to be unregistered.
> --- linux-next-20191209.orig/drivers/devfreq/devfreq-event.c
> +++ linux-next-20191209/drivers/devfreq/devfreq-event.c
> @@ -346,9 +346,9 @@ EXPORT_SYMBOL_GPL(devfreq_event_add_edev
>
> /**
> * devfreq_event_remove_edev() - Remove the devfreq-event device registered.
> - * @dev : the devfreq-event device
> + * @edev : the devfreq-event device
> *
> - * Note that this function remove the registered devfreq-event device.
> + * Note that this function removes the registered devfreq-event device.
> */
> int devfreq_event_remove_edev(struct devfreq_event_dev *edev)
> {
> --- linux-next-20191209.orig/include/linux/devfreq.h
> +++ linux-next-20191209/include/linux/devfreq.h
> @@ -135,6 +135,7 @@ struct devfreq_stats {
> * devfreq.nb to the corresponding register notifier call chain.
> * @work: delayed work for load monitoring.
> * @previous_freq: previously configured frequency value.
> + * @last_status: devfreq user device info, performance statistics
> * @data: Private data of the governor. The devfreq framework does not
> * touch this.
> * @min_freq: Limit minimum frequency requested by user (0: none)
> @@ -148,7 +149,7 @@ struct devfreq_stats {
> * @stats: Statistics of devfreq device behavior
> * @transition_notifier_list: list head of DEVFREQ_TRANSITION_NOTIFIER notifier
> *
> - * This structure stores the devfreq information for a give device.
> + * This structure stores the devfreq information for a given device.
> *
> * Note that when a governor accesses entries in struct devfreq in its
> * functions except for the context of callbacks defined in struct
>
>
>
prev parent reply other threads:[~2019-12-09 4:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191209043427epcas4p434b7d48469d958c23c69eb743de2ade9@epcas4p4.samsung.com>
2019-12-09 4:34 ` Randy Dunlap
2019-12-09 4:43 ` Chanwoo Choi [this message]
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=d4ce2bc5-4a07-f4e8-dffc-ec8a2c120edb@samsung.com \
--to=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rdunlap@infradead.org \
/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
all inboxes | Powered by JetHome®