linux-kernel - Re: [PATCH] ASoC: fsl: fsl_qmc_audio: Remove the logging when parsing channels

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: <172810027430.832098.16999500333273178564.b4-ty@kernel.org>
Date: Sat, 05 Oct 2024 04:51:14 +0100
From: Mark Brown <broonie@...nel.org>
To: Shengjiu Wang <shengjiu.wang@...il.com>, Xiubo Li <Xiubo.Lee@...il.com>, 
 Fabio Estevam <festevam@...il.com>, Nicolin Chen <nicoleotsuka@...il.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Herve Codina <herve.codina@...tlin.com>
Cc: alsa-devel@...a-project.org, linuxppc-dev@...ts.ozlabs.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Christophe Leroy <christophe.leroy@...roup.eu>, 
 Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH] ASoC: fsl: fsl_qmc_audio: Remove the logging when
 parsing channels

On Thu, 03 Oct 2024 14:20:15 +0200, Herve Codina wrote:
> On each channel parsing, a log message is issued. This log message is
> not needed and become annoying when many channels are used (up to 64
> channel supported).
> 
> Simply remove this unneeded log message.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: fsl: fsl_qmc_audio: Remove the logging when parsing channels
      commit: c6e86e19e778553dbedab617aafb25b6bbaf4cd9

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