From: Ewan Milne <emilne@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: James Bottomley <jbottomley@parallels.com>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
DL-MPTFusionLinux@lsi.com, MPT-FusionLinux.pdl@avagotech.com
Subject: Re: [PATCH] fusion: fix excess parameter kernel-doc warning
Date: Mon, 18 Aug 2014 13:07:52 -0400 [thread overview]
Message-ID: <1408381672.1223.212.camel@localhost.localdomain> (raw)
In-Reply-To: <53EFC9E3.6070306@infradead.org>
On Sat, 2014-08-16 at 14:15 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix kernel-doc excess parameter warning:
>
> Warning(..//drivers/message/fusion/mptbase.c:1411): Excess function parameter 'prod_name' description in 'mpt_get_product_name'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: DL-MPTFusionLinux@lsi.com
> Cc: MPT-FusionLinux.pdl@avagotech.com
> ---
> drivers/message/fusion/mptbase.c | 1 -
> 1 file changed, 1 deletion(-)
>
> Index: lnx-317-rc1/drivers/message/fusion/mptbase.c
> ===================================================================
> --- lnx-317-rc1.orig/drivers/message/fusion/mptbase.c
> +++ lnx-317-rc1/drivers/message/fusion/mptbase.c
> @@ -1400,7 +1400,6 @@ mpt_verify_adapter(int iocid, MPT_ADAPTE
> * @vendor: pci vendor id
> * @device: pci device id
> * @revision: pci revision id
> - * @prod_name: string returned
> *
> * Returns product string displayed when driver loads,
> * in /proc/mpt/summary and /sysfs/class/scsi_host/host<X>/version_product
> --
Goes with commit c9834c70efbaaa1461ec04289d97a842244fb294.
Reviewed-by: Ewan D. Milne <emilne@redhat.com>
next prev parent reply other threads:[~2014-08-18 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 21:15 [PATCH] fusion: fix excess parameter kernel-doc warning Randy Dunlap
2014-08-18 17:07 ` Ewan Milne [this message]
2014-08-27 23:47 ` Randy Dunlap
2014-08-28 0:55 ` Christoph Hellwig
2014-08-28 6:28 ` Randy Dunlap
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=1408381672.1223.212.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=MPT-FusionLinux.pdl@avagotech.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).