From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: kbuild test robot <lkp@intel.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
kbuild-all@01.org, gregkh@linuxfoundation.org,
ming.lei@canonical.com, jwboyer@fedoraproject.org,
johannes@sipsolutions.net, luto@amacapital.net, corbet@lwn.net,
dwmw2@infradead.org, dhowells@redhat.com,
seth.forshee@canonical.com, rusty@rustcorp.com.au,
mmarek@suse.cz, mjg59@srcf.ucam.org, kyle@kernel.org,
zohar@linux.vnet.ibm.com, dmitry.kasatkin@gmail.com,
vgoyal@redhat.com, computersforpeace@gmail.com,
keescook@chromium.org, shuahkh@osg.samsung.com,
torvalds@linux-foundation.org,
linux-security-module@vger.kernel.org, keyrings@linux-nfs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/5] firmware: add an extensible system data helpers
Date: Fri, 22 Jan 2016 02:27:33 +0100 [thread overview]
Message-ID: <20160122012733.GI20964@wotan.suse.de> (raw)
In-Reply-To: <201512240608.SVn33hAB%fengguang.wu@intel.com>
On Thu, Dec 24, 2015 at 06:26:39AM +0800, kbuild test robot wrote:
> reproduce: make htmldocs
> >> drivers/base/firmware_class.c:1336: warning: No description found for parameter 'sysdata'
> 1331 /**
> 1332 * release_sysdata_file: - release the resource associated with the sysdata file
> 1333 * @sysdata_file: sysdata resource to release
> 1334 **/
> 1335 void release_sysdata_file(const struct sysdata_file *sysdata)
> > 1336 {
This was a kdoc warning, I've fixed it and this will be part of my
v5 respin.
Luis
next prev parent reply other threads:[~2016-01-22 1:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 21:34 [PATCH v3 0/5] firmware_class: extensible firmware API Luis R. Rodriguez
2015-12-23 21:34 ` [PATCH v3 1/5] firmware: generalize "firmware" as "system data" helpers Luis R. Rodriguez
2016-01-04 20:41 ` Kees Cook
2016-01-22 20:10 ` Luis R. Rodriguez
2015-12-23 21:34 ` [PATCH v3 2/5] firmware: move completing fw into a helper Luis R. Rodriguez
2016-01-04 20:44 ` Josh Boyer
2015-12-23 21:34 ` [PATCH v3 3/5] firmware: fold successful fw read early Luis R. Rodriguez
2016-01-04 20:48 ` Josh Boyer
2016-01-22 1:45 ` Luis R. Rodriguez
2016-01-22 11:56 ` Mimi Zohar
2016-01-22 19:50 ` Luis R. Rodriguez
2015-12-23 21:34 ` [PATCH v3 4/5] firmware: generalize reading file contents as a helper Luis R. Rodriguez
2016-01-22 1:43 ` Luis R. Rodriguez
2015-12-23 21:34 ` [PATCH v3 5/5] firmware: add an extensible system data helpers Luis R. Rodriguez
2015-12-23 22:26 ` kbuild test robot
2016-01-22 1:27 ` Luis R. Rodriguez [this message]
2016-01-04 20:31 ` Kees Cook
2016-01-22 1:58 ` Luis R. Rodriguez
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=20160122012733.GI20964@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=computersforpeace@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=jwboyer@fedoraproject.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=keyrings@linux-nfs.org \
--cc=kyle@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luto@amacapital.net \
--cc=mcgrof@do-not-panic.com \
--cc=ming.lei@canonical.com \
--cc=mjg59@srcf.ucam.org \
--cc=mmarek@suse.cz \
--cc=rusty@rustcorp.com.au \
--cc=seth.forshee@canonical.com \
--cc=shuahkh@osg.samsung.com \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.com \
--cc=zohar@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.