Received-SPF: pass (google.com: domain of linux-kernel+bounces-103366-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com, 
 linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org, 
 Chancel Liu <chancel.liu@nxp.com>
Cc: Zhipeng Wang <zhipeng.wang_1@nxp.com>
In-Reply-To: <20240305065606.3778642-1-chancel.liu@nxp.com>
References: <20240305065606.3778642-1-chancel.liu@nxp.com>
Subject: Re: [PATCH] ASoC: soc-core.c: Skip dummy codec when adding
 platforms
Message-Id: <171042564292.33758.12106139288585646564.b4-ty@kernel.org>
Date: Thu, 14 Mar 2024 14:14:02 +0000
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Tue, 05 Mar 2024 15:56:06 +0900, Chancel Liu wrote:
> When pcm_runtime is adding platform components it will scan all
> registered components. In case of DPCM FE/BE some DAI links will
> configure dummy platform. However both dummy codec and dummy platform
> are using "snd-soc-dummy" as component->name. Dummy codec should be
> skipped when adding platforms otherwise there'll be overflow and UBSAN
> complains.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-core.c: Skip dummy codec when adding platforms
      commit: 23fb6bc2696119391ec3a92ccaffe50e567c515e

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