linux-kernel - Re: [PATCH v2] ASoC: SOF: Makefile: Fix randconfig sof-client build when SND_SOC

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: <164492968840.13815.4226647286187449899.b4-ty@kernel.org>
Date:   Tue, 15 Feb 2022 12:54:48 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
        pierre-louis.bossart@...ux.intel.com, lgirdwood@...il.com,
        ranjani.sridharan@...ux.intel.com
Cc:     fred.oh@...ux.intel.com, daniel.baluta@....com, tiwai@...e.com,
        linux-kernel@...r.kernel.org, kai.vehmanen@...ux.intel.com,
        alsa-devel@...a-project.org
Subject: Re: [PATCH v2] ASoC: SOF: Makefile: Fix randconfig sof-client build when SND_SOC_SOF=y

On Mon, 14 Feb 2022 09:13:30 +0200, Peter Ujfalusi wrote:
> Intel's kernel test robot found the following randconfig combination:
> SND_SOC_SOF=y
> SND_SOC_SOF_CLIENT=m
> 
> In this the sof-client object is not going to be built into the snd-sof.o
> and we will have undefined references to the sof-client functions.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: Makefile: Fix randconfig sof-client build when SND_SOC_SOF=y
      commit: 4965e38fa064056021254af4656b1089a42dc764

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