From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: lgirdwood@gmail.com, broonie@kernel.org,
Luis de Bethencourt <luisbg@osg.samsung.com>
Subject: [PATCH 0/2] regulator: add missing descriptions for docs
Date: Wed, 23 Mar 2016 11:23:24 +0000 [thread overview]
Message-ID: <1458732204-28657-1-git-send-email-luisbg@osg.samsung.com> (raw)
Hi,
I noticed this issues when running make htmldocs. It returns the following
warnings:
.//include/linux/regulator/machine.h:163: warning: No description found for parameter 'over_current_protection'
.//include/linux/regulator/driver.h:205: warning: No description found for parameter 'set_over_current_protection'
.//include/linux/regulator/driver.h:339: warning: No description found for parameter 'csel_reg'
.//include/linux/regulator/driver.h:339: warning: No description found for parameter 'csel_mask'
Thanks,
Luis
Luis de Bethencourt (2):
regulator: add missing description for set_over_current_protection
regulator: add missing descriptions in regulator_desc
include/linux/regulator/driver.h | 5 +++++
1 file changed, 5 insertions(+)
--
2.5.1
next reply other threads:[~2016-03-23 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 11:23 Luis de Bethencourt [this message]
2016-03-23 11:24 ` [PATCH 1/2] regulator: add missing description for set_over_current_protection Luis de Bethencourt
2016-03-23 11:35 ` [PATCH 1/2 v2] " Luis de Bethencourt
2016-03-23 11:45 ` Mark Brown
2016-03-23 11:53 ` Luis de Bethencourt
2016-03-23 13:43 ` Applied "regulator: add missing description for set_over_current_protection" to the regulator tree Mark Brown
2016-03-23 11:24 ` [PATCH 2/2] regulator: add missing descriptions in regulator_desc Luis de Bethencourt
2016-03-23 13:43 ` Applied "regulator: add missing descriptions in regulator_desc" to the regulator tree Mark Brown
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=1458732204-28657-1-git-send-email-luisbg@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®