linux-kernel - Re: [PATCH] ASoC: mediatek: Remove unused mtk_memif_set

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 for Android: free password hash cracker in your pocket

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

Message-Id: <173875947335.32457.7286096499117133517.b4-ty@kernel.org>
Date: Wed, 05 Feb 2025 12:44:33 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com, 
 linux@...blig.org
Cc: linux-sound@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: mediatek: Remove unused mtk_memif_set_rate

On Sat, 01 Feb 2025 00:50:21 +0000, linux@...blig.org wrote:
> mtk_memif_set_rate() has been unused since it was added in the 2019
> commit 9cdf85a19b3a ("ASoC: mediatek: common: add some helpers to control
> mtk_memif")
> 
> Remove it.
> 
> (The _substream version is used, and is left in)
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: Remove unused mtk_memif_set_rate
      commit: c9e9aa80022c6db71bc097a621a6145f39aa0ade

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