linux-kernel - Re: [PATCH v2] ASoC: sti: add missing probe entry for player and reader

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: <172227346114.109775.10465470972478318748.b4-ty@kernel.org>
Date: Mon, 29 Jul 2024 18:17:41 +0100
From: Mark Brown <broonie@...nel.org>
To: Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Jerome Audu <jau@...e.fr>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ASoC: sti: add missing probe entry for player and
 reader

On Sat, 27 Jul 2024 15:40:15 +0200, Jerome Audu wrote:
> This patch addresses a regression in the ASoC STI drivers that was
> introduced in Linux version 6.6.y. The issue originated from a series of
> patches (see https://lore.kernel.org/all/87wmy5b0wt.wl-kuninori.morimoto.gx@renesas.com/)
> that unintentionally omitted necessary probe functions for the player
> and reader components.
> 
> Probe function in `sound/soc/sti/sti_uniperif.c:415` is being replaced
> by another probe function located at `sound/soc/sti/sti_uniperif.c:453`,
> which should instead be derived from the player and reader components.
> This patch correctly reinserts the missing probe entries,
> restoring the intended functionality.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: sti: add missing probe entry for player and reader
      commit: 6b99068d5ea0aa295f15f30afc98db74d056ec7b

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