Re: [PATCH] ASoC: SOF: mediatek: mt8186: Revert Add Google Steelix topology compatible

From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org, cujomalainey@chromium.org
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Trevor Wu <trevor.wu@mediatek.com>,
	Tinghan Shen <tinghan.shen@mediatek.com>
Subject: Re: [PATCH] ASoC: SOF: mediatek: mt8186: Revert Add Google Steelix topology compatible
Date: Wed, 06 Dec 2023 21:04:37 +0000	[thread overview]
Message-ID: <170189667789.80064.8079452528877340900.b4-ty@kernel.org> (raw)
In-Reply-To: <20231205220131.2585913-1-cujomalainey@chromium.org>

On Tue, 05 Dec 2023 14:01:18 -0800, cujomalainey@chromium.org wrote:
> This reverts commit 505c83212da5bfca95109421b8f5d9f8c6cdfef2.
> 
> This is not an official topology from the SOF project. Topologies are
> named based on the card configuration and are NOT board specific.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: SOF: mediatek: mt8186: Revert Add Google Steelix topology compatible
      commit: d20d36755a605a21e737b6b16c566658589b1811

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