linux-kernel - Re: [PATCH] ASoC: mediatek: sof-common: Add NULL check for normal

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: <170500849826.453613.12911028566745797174.b4-ty@kernel.org>
Date: Thu, 11 Jan 2024 21:28:18 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, 
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: perex@...ex.cz, tiwai@...e.com, matthias.bgg@...il.com, 
 trevor.wu@...iatek.com, kuninori.morimoto.gx@...esas.com, 
 chunxu.li@...iatek.com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: sof-common: Add NULL check for
 normal_link string

On Thu, 11 Jan 2024 11:52:26 +0100, AngeloGioacchino Del Regno wrote:
> It's not granted that all entries of struct sof_conn_stream declare
> a `normal_link` (a non-SOF, direct link) string, and this is the case
> for SoCs that support only SOF paths (hence do not support both direct
> and SOF usecases).
> 
> For example, in the case of MT8188 there is no normal_link string in
> any of the sof_conn_stream entries and there will be more drivers
> doing that in the future.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: sof-common: Add NULL check for normal_link string
      commit: e3b3ec967a7d93b9010a5af9a2394c8b5c8f31ed

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