lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 29 Mar 2017 12:02:42 +0100 From: Mark Brown <broonie@...nel.org> To: Tamara Diaconita <diaconitatamara@...il.com> Cc: Tamara Diaconita <diaconita.tamara@...il.com>, Mark Brown <broonie@...nel.org>, lgirdwood@...il.com, broonie@...nel.org, linux-kernel@...r.kernel.org, outreachy-kernel@...glegroups.com, corbet@....net, Tamara Diaconita <diaconita.tamara@...il.com>, linux-kernel@...r.kernel.org Subject: Applied "regulator: core: Fix kerneldoc comments" to the regulator tree The patch regulator: core: Fix kerneldoc comments 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 fffd1133388857f5b4b8c588b41b2ade16c7891c Mon Sep 17 00:00:00 2001 From: Tamara Diaconita <diaconitatamara@...il.com> Date: Tue, 28 Mar 2017 21:30:21 +0300 Subject: [PATCH] regulator: core: Fix kerneldoc comments Remove the description for the non-existing 'ret' to fix the build warning: ./drivers/regulator/core.c:1467: warning: Excess function parameter 'ret' description in 'regulator_dev_lookup'. The description found for the return value is: @ret: 0 on success, -ENODEV if lookup fails permanently, -EPROBE_DEFER if lookup could succeed in the future. Signed-off-by: Tamara Diaconita <diaconita.tamara@...il.com> Signed-off-by: Mark Brown <broonie@...nel.org> --- drivers/regulator/core.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index 49a0b6a2e237..c20b28a63d15 100644 --- a/drivers/regulator/core.c +++ b/drivers/regulator/core.c @@ -1451,8 +1451,6 @@ static struct regulator_dev *regulator_lookup_by_name(const char *name) * regulator_dev_lookup - lookup a regulator device. * @dev: device for regulator "consumer". * @supply: Supply name or regulator ID. - * @ret: 0 on success, -ENODEV if lookup fails permanently, -EPROBE_DEFER if - * lookup could succeed in the future. * * If successful, returns a struct regulator_dev that corresponds to the name * @supply and with the embedded struct device refcount incremented by one. -- 2.11.0
Powered by blists - more mailing lists