Messages in this thread | | | From | Mark Brown <> | Subject | Re: [PATCH] regulator: MAX20086: add gpio/consumer.h | Date | Wed, 19 Jan 2022 18:02:41 +0000 |
| |
On Fri, 14 Jan 2022 19:36:03 -0800, Randy Dunlap wrote: > max20086-regulator.c needs <linux/gpio/consumer.h> for an enum, some > macros, and a function prototype. (seen on ARCH=m68k) > > Adding this header file fixes multiple build errors: > > ../drivers/regulator/max20086-regulator.c: In function 'max20086_i2c_probe': > ../drivers/regulator/max20086-regulator.c:217:26: error: storage size of 'flags' isn't known > 217 | enum gpiod_flags flags; > ../drivers/regulator/max20086-regulator.c:261:27: error: 'GPIOD_OUT_HIGH' undeclared (first use in this function); did you mean 'GPIOF_INIT_HIGH'? > 261 | flags = boot_on ? GPIOD_OUT_HIGH : GPIOD_OUT_LOW; > | ^~~~~~~~~~~~~~ > ../drivers/regulator/max20086-regulator.c:261:44: error: 'GPIOD_OUT_LOW' undeclared (first use in this function); did you mean 'GPIOF_INIT_LOW'? > 261 | flags = boot_on ? GPIOD_OUT_HIGH : GPIOD_OUT_LOW; > ../drivers/regulator/max20086-regulator.c:262:27: error: implicit declaration of function 'devm_gpiod_get'; did you mean 'devm_gpio_free'? [-Werror=implicit-function-declaration] > 262 | chip->ena_gpiod = devm_gpiod_get(chip->dev, "enable", flags); > ../drivers/regulator/max20086-regulator.c:217:26: warning: unused variable 'flags' [-Wunused-variable] > 217 | enum gpiod_flags flags; > > [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-linus
Thanks!
[1/1] regulator: MAX20086: add gpio/consumer.h commit: b4c18c18ebf7cf1e602af88c12ef9cb0d6e5ce51
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
| |