From: Mark Brown <broonie@kernel.org>
To: Luis de Bethencourt <luisbg@osg.samsung.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Applied "regulator: add missing descriptions in regulator_desc" to the regulator tree
Date: Wed, 23 Mar 2016 13:43:01 +0000 [thread overview]
Message-ID: <E1aij3t-0004DI-R4@debutante> (raw)
In-Reply-To: <1458732287-29342-1-git-send-email-luisbg@osg.samsung.com>
The patch
regulator: add missing descriptions in regulator_desc
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
>From d13d3a573be5535123beacd926be38e571097bc5 Mon Sep 17 00:00:00 2001
From: Luis de Bethencourt <luisbg@osg.samsung.com>
Date: Wed, 23 Mar 2016 11:24:47 +0000
Subject: [PATCH] regulator: add missing descriptions in regulator_desc
Members csel_reg and csel_mask of the regulator_desc struct are missing
descriptions for documentation. Adding them.
Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
include/linux/regulator/driver.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/regulator/driver.h b/include/linux/regulator/driver.h
index cd271e89a7e6..01d26244a610 100644
--- a/include/linux/regulator/driver.h
+++ b/include/linux/regulator/driver.h
@@ -255,6 +255,8 @@ enum regulator_type {
*
* @vsel_reg: Register for selector when using regulator_regmap_X_voltage_
* @vsel_mask: Mask for register bitfield used for selector
+ * @csel_reg: Register for TPS65218 LS3 current regulator
+ * @csel_mask: Mask for TPS65218 LS3 current regulator
* @apply_reg: Register for initiate voltage change on the output when
* using regulator_set_voltage_sel_regmap
* @apply_bit: Register bitfield used for initiate voltage change on the
--
2.7.0
prev parent reply other threads:[~2016-03-23 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 11:23 [PATCH 0/2] regulator: add missing descriptions for docs Luis de Bethencourt
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 ` Mark Brown [this message]
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=E1aij3t-0004DI-R4@debutante \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox