Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: rjw@sisk.pl (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM: OPP: opp_find_freq_exact documentation fix
Date: Fri, 25 Feb 2011 23:59:37 +0100	[thread overview]
Message-ID: <201102252359.38140.rjw@sisk.pl> (raw)
In-Reply-To: <1298618044-8292-1-git-send-email-nm@ti.com>

On Friday, February 25, 2011, Nishanth Menon wrote:
> opp_find_freq_exact documentation has is_available instead
> of available. This also fixes warning with the kernel-doc:
> scripts/kernel-doc drivers/base/power/opp.c >/dev/null
> Warning(drivers/base/power/opp.c:246): No description found for parameter 'available'
> Warning(drivers/base/power/opp.c:246): Excess function parameter 'is_available' description in 'opp_find_freq_exact'
> 
> Signed-off-by: Nishanth Menon <nm@ti.com>

Applied to suspend-2.6/linux-next.

Thanks,
Rafael


> ---
>  drivers/base/power/opp.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
> index 2bb9b4c..56a6899 100644
> --- a/drivers/base/power/opp.c
> +++ b/drivers/base/power/opp.c
> @@ -222,7 +222,7 @@ int opp_get_opp_count(struct device *dev)
>   * opp_find_freq_exact() - search for an exact frequency
>   * @dev:		device for which we do this operation
>   * @freq:		frequency to search for
> - * @is_available:	true/false - match for available opp
> + * @available:		true/false - match for available opp
>   *
>   * Searches for exact match in the opp list and returns pointer to the matching
>   * opp if found, else returns ERR_PTR in case of error and should be handled
> 

      reply	other threads:[~2011-02-25 22:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  7:14 [PATCH] PM: OPP: opp_find_freq_exact documentation fix Nishanth Menon
2011-02-25 22:59 ` Rafael J. Wysocki [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=201102252359.38140.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-arm-kernel@lists.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