linux-kernel - Re: [PATCH v3] ASoC: tpa6130: use i2c_match

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <165159306303.184114.6148689854400519585.b4-ty@kernel.org>
Date:   Tue, 03 May 2022 16:51:03 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, steve@....org
Cc:     linux-kernel@...r.kernel.org, wsa@...nel.org
Subject: Re: [PATCH v3] ASoC: tpa6130: use i2c_match_id and simple i2c probe

On Sun, 1 May 2022 19:10:09 +0200, Stephen Kitt wrote:
> As part of the ongoing i2c transition to the simple probe
> ("probe_new"), this patch uses i2c_match_id to retrieve the
> driver_data for the probed device. The id parameter is thus no longer
> necessary and the simple probe can be used instead.
> 
> The i2c id table is moved up before the probe function, as suggested
> by Wolfram Sang.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: tpa6130: use i2c_match_id and simple i2c probe
      commit: 55d2a66cfec6a4196243940f754f5b34dd2106bf

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