linux-kernel - Re: [PATCH] ASoC: img: Imagination Technologies sound should depend on MIPS

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: <175206098407.674109.10318726327489121881.b4-ty@kernel.org>
Date: Wed, 09 Jul 2025 12:36:24 +0100
From: Mark Brown <broonie@...nel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
 Rahul Bedarkar <rahulbedarkar89@...il.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Geert Uytterhoeven <geert+renesas@...der.be>
Cc: linux-sound@...r.kernel.org, linux-mips@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: img: Imagination Technologies sound should
 depend on MIPS

On Tue, 08 Jul 2025 17:47:29 +0200, Geert Uytterhoeven wrote:
> Before, all Imagination sound symbols were gated by the SND_SOC_IMG
> symbol, offering the user a simple option to hide them all.  After the
> removal of this gate symbol, all symbols are exposed to the user, even
> when configuring a kernel for a non-Imagination platform.
> Fix this by adding a dependency on MIPS, to prevent asking the user
> about these drivers when configuring a kernel for a different
> architecture.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: img: Imagination Technologies sound should depend on MIPS
      commit: 68e4dadacb7faa393b532b41bbf99a2dbfec3b1b

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