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 4328/4460] DockBook: include/linux/rio.h:299: warning: No description found for parameter 'lock'
Date: Wed, 10 Feb 2016 18:17:33 +0800 [thread overview]
Message-ID: <201602101826.QDarM4nZ%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2823 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b613c2bfa3e843fdeff95878edc7326b763abd1b
commit: 4e1ba9ee9d1f2c27facd8772e40ee72ee6e4e1d8 [4328/4460] rapidio: add lock protection for doorbell list
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
>> include/linux/rio.h:299: warning: No description found for parameter 'lock'
>> include/linux/rio.h:299: warning: Excess struct/union/enum/typedef member 'mutex' description in 'rio_mport'
include/linux/rio.h:332: warning: No description found for parameter 'dev'
vim +/lock +299 include/linux/rio.h
70a50ebd Matt Porter 2005-11-07 283 unsigned char index; /* port index, unique among all port
70a50ebd Matt Porter 2005-11-07 284 interfaces of the same type */
e0423236 Zhang Wei 2008-04-18 285 unsigned int sys_size; /* RapidIO common transport system size.
e0423236 Zhang Wei 2008-04-18 286 * 0 - Small size. 256 devices.
e0423236 Zhang Wei 2008-04-18 287 * 1 - Large size, 65536 devices.
e0423236 Zhang Wei 2008-04-18 288 */
61b26917 Zhang Wei 2008-04-18 289 enum rio_phy_type phy_type; /* RapidIO phy type */
af84ca38 Alexandre Bounine 2010-10-27 290 u32 phys_efptr;
ed43f44f Alexandre Bounine 2012-10-04 291 unsigned char name[RIO_MAX_MPORT_NAME];
2aaf308b Alexandre Bounine 2014-04-07 292 struct device dev;
ad1e9380 Zhang Wei 2008-04-18 293 void *priv; /* Master port private data */
e42d98eb Alexandre Bounine 2012-05-31 294 #ifdef CONFIG_RAPIDIO_DMA_ENGINE
e42d98eb Alexandre Bounine 2012-05-31 295 struct dma_device dma;
e42d98eb Alexandre Bounine 2012-05-31 296 #endif
a11650e1 Alexandre Bounine 2013-05-24 297 struct rio_scan *nscan;
cb317a8b Alexandre Bounine 2016-02-10 298 atomic_t state;
70a50ebd Matt Porter 2005-11-07 @299 };
70a50ebd Matt Porter 2005-11-07 300
cb317a8b Alexandre Bounine 2016-02-10 301 static inline int rio_mport_is_running(struct rio_mport *mport)
cb317a8b Alexandre Bounine 2016-02-10 302 {
cb317a8b Alexandre Bounine 2016-02-10 303 return atomic_read(&mport->state) == RIO_DEVICE_RUNNING;
cb317a8b Alexandre Bounine 2016-02-10 304 }
cb317a8b Alexandre Bounine 2016-02-10 305
bc8fcfea Alexandre Bounine 2013-05-24 306 /*
bc8fcfea Alexandre Bounine 2013-05-24 307 * Enumeration/discovery control flags
:::::: The code at line 299 was first introduced by commit
:::::: 70a50ebd9a94533964c19f918dbbd66763e3f9e5 [PATCH] RapidIO support: core includes
:::::: TO: Matt Porter <mporter@kernel.crashing.org>
:::::: CC: Linus Torvalds <torvalds@g5.osdl.org>
---
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 10:18 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=201602101826.QDarM4nZ%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