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 4322/4460] DockBook: include/linux/rio.h:314: warning: No description found for parameter 'dev'
Date: Wed, 10 Feb 2016 17:27:00 +0800 [thread overview]
Message-ID: <201602101752.DxyjGKaa%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2923 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b613c2bfa3e843fdeff95878edc7326b763abd1b
commit: c8697cdc157b6d3cf6e3963b41a41e8528cb66bd [4322/4460] rapidio: move net allocation into core code
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
>> include/linux/rio.h:314: warning: No description found for parameter 'dev'
vim +/dev +314 include/linux/rio.h
70a50ebd Matt Porter 2005-11-07 298 * @mports: List of master ports accessing this network
70a50ebd Matt Porter 2005-11-07 299 * @hport: Default port for accessing this network
70a50ebd Matt Porter 2005-11-07 300 * @id: RIO network ID
c8697cdc Alexandre Bounine 2016-02-10 301 * @enum_data: private data specific to a network enumerator
c8697cdc Alexandre Bounine 2016-02-10 302 * @release: enumerator-specific release callback
70a50ebd Matt Porter 2005-11-07 303 */
70a50ebd Matt Porter 2005-11-07 304 struct rio_net {
70a50ebd Matt Porter 2005-11-07 305 struct list_head node; /* node in list of networks */
70a50ebd Matt Porter 2005-11-07 306 struct list_head devices; /* list of devices in this net */
a7071efc Alexandre Bounine 2012-10-04 307 struct list_head switches; /* list of switches in this net */
70a50ebd Matt Porter 2005-11-07 308 struct list_head mports; /* list of ports accessing net */
70a50ebd Matt Porter 2005-11-07 309 struct rio_mport *hport; /* primary port for accessing net */
70a50ebd Matt Porter 2005-11-07 310 unsigned char id; /* RIO network ID */
c8697cdc Alexandre Bounine 2016-02-10 311 struct device dev;
c8697cdc Alexandre Bounine 2016-02-10 312 void *enum_data; /* private data for enumerator of the network */
c8697cdc Alexandre Bounine 2016-02-10 313 void (*release)(struct rio_net *net);
70a50ebd Matt Porter 2005-11-07 @314 };
70a50ebd Matt Porter 2005-11-07 315
01af651e Alexandre Bounine 2016-02-10 316 enum rio_link_speed {
01af651e Alexandre Bounine 2016-02-10 317 RIO_LINK_DOWN = 0, /* SRIO Link not initialized */
01af651e Alexandre Bounine 2016-02-10 318 RIO_LINK_125 = 1, /* 1.25 GBaud */
01af651e Alexandre Bounine 2016-02-10 319 RIO_LINK_250 = 2, /* 2.5 GBaud */
01af651e Alexandre Bounine 2016-02-10 320 RIO_LINK_312 = 3, /* 3.125 GBaud */
01af651e Alexandre Bounine 2016-02-10 321 RIO_LINK_500 = 4, /* 5.0 GBaud */
01af651e Alexandre Bounine 2016-02-10 322 RIO_LINK_625 = 5 /* 6.25 GBaud */
:::::: The code at line 314 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 9:27 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=201602101752.DxyjGKaa%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