ASoC: wm8731: use simple i2c probe function
Subsystems (3)
PATCH 1/1 ASoC: wm8731: use simple i2c probe function
The i2c probe functions here don't use the id information provided in their second argument, so the single-parameter i2c probe function ("probe_new") can be used instead.
This avoids scanning the identifier tables during probes.
--- sound/soc/codecs/wm8731.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
sound/soc/codecs/wm8731.c +2 -3
@@ -723,8 +723,7 @@ static struct spi_driver wm8731_spi_driver = {#endif /* CONFIG_SPI_MASTER */ #if IS_ENABLED (CONFIG_I2C ) -static int wm8731_i2c_probe (struct i2c_client *i2c, -const struct i2c_device_id *id) +static int wm8731_i2c_probe (struct i2c_client *i2c) {struct wm8731_priv *wm8731;int ret;
@@ -788,7 +787,7 @@ static struct i2c_driver wm8731_i2c_driver = { .name = "wm8731", .of_match_table = wm8731_of_match, }, - .probe = wm8731_i2c_probe, + .probe_new = wm8731_i2c_probe, .id_table = wm8731_i2c_id, };#endif
Signature · 1 line
2.27.0
Mark Brown
maintainerQuoted 3 lines · Stephen Kitt
The i2c probe functions here don't use the id information provided in their second argument, so the single-parameter i2c probe function ("
probe_new") can be used instead.
This doesn't apply against current code, please check and resend.
Mark Brown
maintainerQuoted 8 lines · Stephen Kitt
The i2c probe functions here don't use the id information provided in their second argument, so the single-parameter i2c probe function ("
probe_new") can be used instead.This avoids scanning the identifier tables during probes.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: wm8731: use simple i2c probe function
commit: 40658542d7713b6f1b51556ef91822f9ca8942d0
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