linux-kernel - Re: [PATCH] ASoC: test-component: add set_tdm

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: <174437879941.1666456.2351901600646571889.b4-ty@kernel.org>
Date: Fri, 11 Apr 2025 14:39:59 +0100
From: Mark Brown <broonie@...nel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Nicolas Frattaroli <nicolas.frattaroli@...labora.com>
Cc: Daniel Baluta <daniel.baluta@...il.com>, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, kernel@...labora.com
Subject: Re: [PATCH] ASoC: test-component: add set_tdm_slot stub
 implementation

On Thu, 10 Apr 2025 21:25:32 +0200, Nicolas Frattaroli wrote:
> The test-component driver implements various stub callbacks. One
> of the ones it doesn't implement is set_tdm_slot. This has no
> functional impact on whether ASoC core believes test-component to
> do TDM or not, it just means that any TDM configuration can't
> readily be dumped for debugging purposes like it can with the other
> callbacks.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: test-component: add set_tdm_slot stub implementation
      commit: e78e7856d233010e6afef62f15567a8e7777c8bc

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