linux-kernel - Re: [PATCH] ASoC: doc: dapm: Add location information for dapm-graph tool

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: <173254406059.44664.4605735086287465083.b4-ty@kernel.org>
Date: Mon, 25 Nov 2024 14:14:20 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, corbet@....net, 
 anish kumar <yesanishhere@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, 
 linux-sound@...r.kernel.org
Subject: Re: [PATCH] ASoC: doc: dapm: Add location information for
 dapm-graph tool

On Thu, 21 Nov 2024 15:29:58 -0800, anish kumar wrote:
> To help developers debug DAPM issues and visualize widget connectivity,
> the dapm-graph tool provides a graphical representation of how widgets
> and routes are connected. This commit adds the location information for
> the tool to the documentation, making it easier for users to find and
> use it for troubleshooting DAPM-related problems.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: doc: dapm: Add location information for dapm-graph tool
      commit: 8697ecc3274214c65ff271a58e7abb601216f2a8

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