From: Randy Dunlap <rdunlap@xenotime.net>
To: Nishanth Menon <nm@ti.com>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Kevin Hilman <khilman@ti.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / devfreq: kernel-doc typo corrections
Date: Thu, 11 Oct 2012 11:22:20 -0700 [thread overview]
Message-ID: <50770E5C.4040302@xenotime.net> (raw)
In-Reply-To: <1349962755-19598-1-git-send-email-nm@ti.com>
On 10/11/2012 06:39 AM, Nishanth Menon wrote:
> Parameter documentation needs a ':' for scripts/kernel-doc
> to parse properly.
>
> Minor fixes for ones warned by:
> ./scripts/kernel-doc -text drivers/devfreq/devfreq.c>/dev/null
>
> Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
> Cc: Kevin Hilman <khilman@ti.com>
> Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-pm@vger.kernel.org
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks.
> ---
> drivers/devfreq/devfreq.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
> index 70c31d4..e4d48d2 100644
> --- a/drivers/devfreq/devfreq.c
> +++ b/drivers/devfreq/devfreq.c
> @@ -123,9 +123,9 @@ int update_devfreq(struct devfreq *devfreq)
> /**
> * devfreq_notifier_call() - Notify that the device frequency requirements
> * has been changed out of devfreq framework.
> - * @nb the notifier_block (supposed to be devfreq->nb)
> - * @type not used
> - * @devp not used
> + * @nb: the notifier_block (supposed to be devfreq->nb)
> + * @type: not used
> + * @devp: not used
> *
> * Called by a notifier that uses devfreq->nb.
> */
> @@ -431,7 +431,7 @@ err_out:
>
> /**
> * devfreq_remove_device() - Remove devfreq feature from a device.
> - * @devfreq the devfreq instance to be removed
> + * @devfreq: the devfreq instance to be removed
> */
> int devfreq_remove_device(struct devfreq *devfreq)
> {
> @@ -641,9 +641,9 @@ module_exit(devfreq_exit);
> /**
> * devfreq_recommended_opp() - Helper function to get proper OPP for the
> * freq value given to target callback.
> - * @dev The devfreq user device. (parent of devfreq)
> - * @freq The frequency given to target function
> - * @flags Flags handed from devfreq framework.
> + * @dev: The devfreq user device. (parent of devfreq)
> + * @freq: The frequency given to target function
> + * @flags: Flags handed from devfreq framework.
> *
> */
> struct opp *devfreq_recommended_opp(struct device *dev, unsigned long *freq,
> @@ -674,8 +674,8 @@ struct opp *devfreq_recommended_opp(struct device *dev, unsigned long *freq,
> * devfreq_register_opp_notifier() - Helper function to get devfreq notified
> * for any changes in the OPP availability
> * changes
> - * @dev The devfreq user device. (parent of devfreq)
> - * @devfreq The devfreq object.
> + * @dev: The devfreq user device. (parent of devfreq)
> + * @devfreq: The devfreq object.
> */
> int devfreq_register_opp_notifier(struct device *dev, struct devfreq *devfreq)
> {
> @@ -690,8 +690,8 @@ int devfreq_register_opp_notifier(struct device *dev, struct devfreq *devfreq)
> * devfreq_unregister_opp_notifier() - Helper function to stop getting devfreq
> * notified for any changes in the OPP
> * availability changes anymore.
> - * @dev The devfreq user device. (parent of devfreq)
> - * @devfreq The devfreq object.
> + * @dev: The devfreq user device. (parent of devfreq)
> + * @devfreq: The devfreq object.
> *
> * At exit() callback of devfreq_dev_profile, this must be included if
> * devfreq_recommended_opp is used.
--
~Randy
next prev parent reply other threads:[~2012-10-11 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 13:39 [PATCH] PM / devfreq: kernel-doc typo corrections Nishanth Menon
2012-10-11 18:22 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-17 4:57 MyungJoo Ham
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=50770E5C.4040302@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=khilman@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=rjw@sisk.pl \
/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