All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jianjun Kong <jianjun@zeuux.org>
Cc: Linux-Kernel-Mailing-List <linux-kernel@vger.kernel.org>,
	mporter@kernel.crashing.org
Subject: Re: [PATCH] rapidio: fix kernel-doc warning
Date: Wed, 31 Dec 2008 20:39:50 -0800	[thread overview]
Message-ID: <495C4916.3080700@oracle.com> (raw)
In-Reply-To: <20090101043749.GA14614@ubuntu>

Jianjun Kong wrote:
> rapidio: fix kernel-doc warning
> 
> Fix kernel-doc parameter warning and correct the descriptio:
> Warning(/media/sda1/Project/linux-2.6//drivers/rapidio/rio-driver.c:88): Excess function parameter 'id'
> description in 'rio_device_probe'
> The parameter 'id' may be deleted.
> 
> Signed-off-by: Jianjun Kong <jianjun@zeuux.org>
> Cc: Matt Porter <mporter@kernel.crashing.org>

Hi and thanks, but this is already fixed in Andrew Morton's mm patch series.
You should probably check there for other such patches.


> ---
>  drivers/rapidio/rio-driver.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/rapidio/rio-driver.c b/drivers/rapidio/rio-driver.c
> index 956d3e7..cd6f14e 100644
> --- a/drivers/rapidio/rio-driver.c
> +++ b/drivers/rapidio/rio-driver.c
> @@ -78,8 +78,7 @@ void rio_dev_put(struct rio_dev *rdev)
>  }
>  
>  /**
> - *  rio_device_probe - Tell if a RIO device structure has a matching RIO device id structure
> - *  @id: the RIO device id structure to match against
> + *  rio_device_probe - Tell if a RIO device structure has a matching RIO device structure
>   *  @dev: the RIO device structure to match against
>   *
>   * return 0 and set rio_dev->driver when drv claims rio_dev, else error


-- 
~Randy

      reply	other threads:[~2009-01-01  4:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01  4:37 [PATCH] rapidio: fix kernel-doc warning Jianjun Kong
2009-01-01  4:39 ` Randy Dunlap [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=495C4916.3080700@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=jianjun@zeuux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mporter@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.