linux-kernel - Re: [PATCH 0/2] ASoC: trace: trace more parameters in ASoC DAPM events

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: <170973855626.169634.1190336120832781650.b4-ty@kernel.org>
Date: Wed, 06 Mar 2024 15:22:36 +0000
From: Mark Brown <broonie@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>, 
 Masami Hiramatsu <mhiramat@...nel.org>, 
 Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Luca Ceresoli <luca.ceresoli@...tlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@...tlin.com>, 
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, 
 linux-sound@...r.kernel.org
Subject: Re: [PATCH 0/2] ASoC: trace: trace more parameters in ASoC DAPM
 events

On Wed, 06 Mar 2024 10:29:59 +0100, Luca Ceresoli wrote:
> This small series adds parameters to existing DAPM trace events to make
> them more informative.
> 
> 

Applied to

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

Thanks!

[1/2] ASoC: trace: add component to set_bias_level trace events
      commit: 6ef46a69ec32fe1cf56de67742fcd01af4bf48af
[2/2] ASoC: trace: add event to snd_soc_dapm trace events
      commit: 7df3eb4cdb6bbfa482f51548b9fd47c2723c68ba

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