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: Mon, 31 Jan 2022 15:19:38 +0000 From: Mark Brown <broonie@...nel.org> To: linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org> Cc: Liam Girdwood <lgirdwood@...il.com>, Takashi Iwai <tiwai@...e.com>, Alejandro Tafalla <atafalla@...on.com>, alsa-devel@...a-project.org, kernel test robot <lkp@...el.com> Subject: Re: [PATCH] ASoC: max98927: add missing header file On Sat, 29 Jan 2022 00:02:59 -0800, Randy Dunlap wrote: > Add a header file that provides the missing function prototypes > and macro to fix these build errors (seen on arch/alpha/): > > ../sound/soc/codecs/max98927.c: In function 'max98927_i2c_probe': > ../sound/soc/codecs/max98927.c:902:19: error: implicit declaration of function 'devm_gpiod_get_optional'; did you mean 'devm_regulator_get_optional'? [-Werror=implicit-function-declaration] > 902 | = devm_gpiod_get_optional(&i2c->dev, "reset", GPIOD_OUT_HIGH); > | ^~~~~~~~~~~~~~~~~~~~~~~ > ../sound/soc/codecs/max98927.c:902:63: error: 'GPIOD_OUT_HIGH' undeclared (first use in this function); did you mean 'GPIOF_INIT_HIGH'? > 902 | = devm_gpiod_get_optional(&i2c->dev, "reset", GPIOD_OUT_HIGH); > | ^~~~~~~~~~~~~~ > ../sound/soc/codecs/max98927.c:909:17: error: implicit declaration of function 'gpiod_set_value_cansleep'; did you mean 'gpio_set_value_cansleep'? [-Werror=implicit-function-declaration] > 909 | gpiod_set_value_cansleep(max98927->reset_gpio, 0); > | ^~~~~~~~~~~~~~~~~~~~~~~~ > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: max98927: add missing header file commit: bb45f689fa62110c263c86070bfcb9ecbb6e1e23 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
Powered by blists - more mailing lists