linux-kernel - Re: [PATCH v2 0/2] ASoc: simple-mux: Allow to specify an idle-state

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: <173160348868.529304.8793310575318436684.b4-ty@kernel.org>
Date: Thu, 14 Nov 2024 16:58:08 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, 
 Alexandre Belloni <aleandre.belloni@...tlin.com>, 
 "Hendrik v. Raven" <h.v.raven@...zmedtech.de>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org
Subject: Re: [PATCH v2 0/2] ASoc: simple-mux: Allow to specify an
 idle-state

On Thu, 14 Nov 2024 12:01:24 +0100, Hendrik v. Raven wrote:
> This series adds support for the idle-state property from the mux
> framework to the simple-mux audio variant. It allows to specify the state
> of the mux when it is not in use.
> 
> 

Applied to

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

Thanks!

[1/2] ASoc: simple-mux: add idle-state support
      commit: 2b974284aa073d6e2936f9032e8ad7b99480b5b8
[2/2] ASoC: dt-bindings: simple-mux: add idle-state property
      commit: 3b7e11a0116c30848d44429650ad80f9cc3bd963

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