mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Marcos Paulo Souza <marcos.mage@gmail.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: base: platform.c: Fix warning on make htmldocs
Date: Mon, 15 Aug 2011 09:12:41 -0700	[thread overview]
Message-ID: <20110815091241.78672ff5.rdunlap@xenotime.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1108151258310.4595@odin>

On Mon, 15 Aug 2011 13:02:11 -0300 (BRT) Marcos Paulo Souza wrote:

> 
> The function arch_setup_pdev_archdata has a parameter called pdev, but the 
> documentation of the function documents a dev parameter. By changing the 
> documentation parameter to pdev fix this warning.
> 
> Signed-off-by: Marcos Paulo de Souza <marcos.mage@gmail.com>
> 
> ---
>  drivers/base/platform.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> index 0cad9c7..99a5272 100644
> --- a/drivers/base/platform.c
> +++ b/drivers/base/platform.c
> @@ -33,7 +33,7 @@ EXPORT_SYMBOL_GPL(platform_bus);
>  
>  /**
>   * arch_setup_pdev_archdata - Allow manipulation of archdata before its used
> - * @dev: platform device
> + * @pdev: platform device
>   *
>   * This is called before platform_device_add() such that any pdev_archdata may
>   * be setup before the platform_notifier is called.  So if a user needs to
> -- 

This is already fixed in linux-next.  It's probably a good idea to
check linux-next for fixes etc.

Thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2011-08-15 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 16:02 Marcos Paulo Souza
2011-08-15 16:12 ` 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=20110815091241.78672ff5.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcos.mage@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

all inboxes | Powered by JetHome®