linux-kernel - Re: [PATCH] ASoC: simple-mux: add read 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]

Message-Id: <166749329885.480833.18370914734469838368.b4-ty@kernel.org>
Date:   Thu, 03 Nov 2022 16:34:58 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Maarten Zanders <maarten.zanders@...d.be>,
        Takashi Iwai <tiwai@...e.com>
Cc:     alexandre.belloni@...tlin.com,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: simple-mux: add read function

On Fri, 28 Oct 2022 21:13:01 +0200, Maarten Zanders wrote:
> During initialisation DAPM tries to read the state of the MUX
> being connected, resulting in this error log:
> input-mux: ASoC: error at soc_component_read_no_lock on input-mux: -5
> 
> Provide a read function which allows DAPM to read the state of the
> MUX.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: simple-mux: add read function
      commit: f7d97cb564a2ac5517ee7cc933de729e533d659a

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