linux-kernel - Re: [PATCH] ASoC: tegra: Remove the isomgr

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: <173945697410.151957.234368627529558399.b4-ty@kernel.org>
Date: Thu, 13 Feb 2025 14:29:34 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, "Sheetal ." <sheetal@...dia.com>
Cc: linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org, 
 jonathanh@...dia.com, thierry.reding@...il.com, mkumard@...dia.com, 
 spujar@...dia.com
Subject: Re: [PATCH] ASoC: tegra: Remove the isomgr_bw APIs export

On Thu, 13 Feb 2025 11:12:16 +0000, Sheetal . wrote:
> Commit 4a91fe4c0d683 ("ASoC: tegra: Add interconnect support") exported
> tegra_isomgr_adma_setbw, tegra_isomgr_adma_register and
> tegra_isomgr_adma_register APIs, but there are no users of these that
> required these symbols to be exported.
> Hence, remove the exporting of the symbols.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tegra: Remove the isomgr_bw APIs export
      commit: ae575d2145d1a2c8bb5d2835d7d54751f3b0bace

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