From: kbuild test robot <fengguang.wu@intel.com>
To: Alexandre Bounine <alexandre.bounine@idt.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 4330/4460] DockBook: drivers/rapidio/rio.c:568: warning: No description found for parameter 'mport'
Date: Wed, 10 Feb 2016 19:06:28 +0800 [thread overview]
Message-ID: <201602101926.kxEbVffs%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b613c2bfa3e843fdeff95878edc7326b763abd1b
commit: 6d643d52a9d10ccf67d6990ff28c9042ab68f473 [4330/4460] rapidio: move rio_pw_enable into core code
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
>> drivers/rapidio/rio.c:568: warning: No description found for parameter 'mport'
>> drivers/rapidio/rio.c:568: warning: Excess function parameter 'port' description in 'rio_pw_enable'
include/linux/rio.h:301: warning: No description found for parameter 'lock'
include/linux/rio.h:301: warning: Excess struct/union/enum/typedef member 'mutex' description in 'rio_mport'
include/linux/rio.h:334: warning: No description found for parameter 'dev'
>> drivers/rapidio/rio.c:568: warning: No description found for parameter 'mport'
>> drivers/rapidio/rio.c:568: warning: Excess function parameter 'port' description in 'rio_pw_enable'
vim +/mport +568 drivers/rapidio/rio.c
552 if (rdev->pwcback) {
553 rdev->pwcback = NULL;
554 rc = 0;
555 }
556
557 spin_unlock(&rio_global_list_lock);
558 return rc;
559 }
560 EXPORT_SYMBOL_GPL(rio_release_inb_pwrite);
561
562 /**
563 * rio_pw_enable - Enables/disables port-write handling by a master port
564 * @port: Master port associated with port-write handling
565 * @enable: 1=enable, 0=disable
566 */
567 void rio_pw_enable(struct rio_mport *mport, int enable)
> 568 {
569 if (mport->ops->pwenable) {
570 mutex_lock(&mport->lock);
571
572 if ((enable && ++mport->pwe_refcnt == 1) ||
573 (!enable && mport->pwe_refcnt && --mport->pwe_refcnt == 0))
574 mport->ops->pwenable(mport, enable);
575 mutex_unlock(&mport->lock);
576 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6276 bytes --]
reply other threads:[~2016-02-10 11:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201602101926.kxEbVffs%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.bounine@idt.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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