diff options
author | Arnd Bergmann <arnd@arndb.de> | 2015-11-20 17:24:39 +0300 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2015-11-20 21:04:34 +0300 |
commit | fa731ac7ea04a7d3a5c6d2f568132478c02a83b3 (patch) | |
tree | 0dcbbc22aa5caf40c7d5325c048486bde4e8cea8 /fs | |
parent | 8005c49d9aea74d382f474ce11afbbc7d7130bec (diff) | |
download | linux-fa731ac7ea04a7d3a5c6d2f568132478c02a83b3.tar.xz |
regulator: core: avoid unused variable warning
The second argument of the mutex_lock_nested() helper is only
evaluated if CONFIG_DEBUG_LOCK_ALLOC is set. Otherwise we
get this build warning for the new regulator_lock_supply
function:
drivers/regulator/core.c: In function 'regulator_lock_supply':
drivers/regulator/core.c:142:6: warning: unused variable 'i' [-Wunused-variable]
To avoid the warning, this restructures the code to make it
both simpler and to move the 'i++' outside of the mutex_lock_nested
call, where it is now always used and the variable is not
flagged as unused.
We had some discussion about changing mutex_lock_nested to an
inline function, which would make the code do the right thing here,
but in the end decided against it, in order to guarantee that
mutex_lock_nested() does not introduced overhead without
CONFIG_DEBUG_LOCK_ALLOC.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Fixes: 9f01cd4a915 ("regulator: core: introduce function to lock regulators and its supplies")
Link: http://permalink.gmane.org/gmane.linux.kernel/2068900
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions