linux-kernel - Re: [PATCH] ASoC: tracing: Export SND_SOC_DAPM_DIR

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Wed, 17 Apr 2024 09:12:05 +0900
From: Mark Brown <broonie@...nel.org>
To: LKML <linux-kernel@...r.kernel.org>, 
 Linux trace kernel <linux-trace-kernel@...r.kernel.org>, 
 Steven Rostedt <rostedt@...dmis.org>
Cc: Masami Hiramatsu <mhiramat@...nel.org>, 
 Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, 
 Luca Ceresoli <luca.ceresoli@...tlin.com>, 
 Lars-Peter Clausen <lars@...afoo.de>
Subject: Re: [PATCH] ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its
 value

On Tue, 16 Apr 2024 00:03:03 -0400, Steven Rostedt wrote:
> The string SND_SOC_DAPM_DIR_OUT is printed in the snd_soc_dapm_path trace
> event instead of its value:
> 
>    (((REC->path_dir) == SND_SOC_DAPM_DIR_OUT) ? "->" : "<-")
> 
> User space cannot parse this, as it has no idea what SND_SOC_DAPM_DIR_OUT
> is. Use TRACE_DEFINE_ENUM() to convert it to its value:
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value
      commit: 58300f8d6a48e58d1843199be743f819e2791ea3

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