linux-kernel - Re: [PATCH] ASoC: sun8i-codec: Hook up component probe function

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]

Date:   Wed, 19 Aug 2020 13:15:35 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Samuel Holland <samuel@...lland.org>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
        Maxime Ripard <mripard@...nel.org>,
        linux-kernel@...r.kernel.org,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Chen-Yu Tsai <wens@...e.org>
Subject: Re: [PATCH] ASoC: sun8i-codec: Hook up component probe function

On Tue, 18 Aug 2020 22:40:38 -0500, Samuel Holland wrote:
> Due to a mistake made while reordering patches, commit 90cac932976e
> ("ASoC: sun8i-codec: Fix DAPM to match the hardware topology") added
> the sun8i_codec_component_probe function without referencing it from
> the component definition. Add the reference so the probe function gets
> called as expected.

Applied to

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

Thanks!

[1/1] ASoC: sun8i-codec: Hook up component probe function
      commit: ed7f0fbc9dca0961ac9a713c778319b7f24315ae

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