linux-kernel - Re: [PATCH RESEND 0/3] ASoC: dapm-graph: add component on/off and route names to graph

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: <172449440543.846858.4694040837255078540.b4-ty@kernel.org>
Date: Sat, 24 Aug 2024 11:13:25 +0100
From: Mark Brown <broonie@...nel.org>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>, 
 Thomas Petazzoni <thomas.petazzoni@...tlin.com>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Luca Ceresoli <luca.ceresoli@...tlin.com>
Subject: Re: [PATCH RESEND 0/3] ASoC: dapm-graph: add component on/off and
 route names to graph

On Fri, 23 Aug 2024 09:45:58 +0200, Luca Ceresoli wrote:
> This small series adds some improvements to dapm-graph in order to produce
> a more correct and informative graph.
> 
> 

Applied to

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

Thanks!

[1/3] ASoC: dapm-graph: remove the "ROOT" cluster
      commit: 5a98c2e5399b125231ebb4594fee5fddfb7db9fd
[2/3] ASoC: dapm-graph: visualize component On/Off bias level
      commit: 64a1e3ddab1ebaa590101b0d7d7fa5d3144da1e8
[3/3] ASoC: dapm-graph: show path name for non-static routes
      commit: a14b278a47dd4b263799214c5ae0da6506ed7692

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