[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169989208005.3289099.6135603822989118878.b4-ty@kernel.org>
Date: Mon, 13 Nov 2023 16:14:40 +0000
From: Mark Brown <broonie@...nel.org>
To: pierre-louis.bossart@...ux.intel.com,
peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
ranjani.sridharan@...ux.intel.com, kai.vehmanen@...ux.intel.com,
daniel.baluta@....com, lgirdwood@...il.com, tiwai@...e.com,
perex@...ex.cz, matthias.bgg@...il.com,
angelogioacchino.delregno@...labora.com,
Trevor Wu <trevor.wu@...iatek.com>
Cc: yc.hung@...iatek.com, sound-open-firmware@...a-project.org,
alsa-devel@...a-project.org, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] ASoC: SOF: mediatek: remove unused variables
On Fri, 03 Nov 2023 17:54:29 +0800, Trevor Wu wrote:
> There are some variables that are no longer being used because they
> were declared for the deprecated memory layout. Currently, these code
> sections confuse the users. Therefore, this series removes the code
> that was implemented for those variables.
>
> Trevor Wu (3):
> ASoC: SOF: mediatek: mt8195: clean up unused code
> ASoC: SOF: mediatek: mt8186: clean up unused code
> ASoC: SOF: mediatek: remove unused variables
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: SOF: mediatek: mt8195: clean up unused code
commit: ab475966455ce285c2c9978a3e3bfe97d75ff8d4
[2/3] ASoC: SOF: mediatek: mt8186: clean up unused code
commit: a4de5a345cf76c6f294a906e11c2fb675a46fd3d
[3/3] ASoC: SOF: mediatek: remove unused variables
commit: 82e340ca3f25dc3ddd20e88e3606ed9006f90f5d
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
Powered by blists - more mailing lists