mbox series

[0/2] ASoC: mt8192: Address spammy log messages

Message ID 20230313212908.2282961-1-nfraprado@collabora.com (mailing list archive)
Headers show
Series ASoC: mt8192: Address spammy log messages | expand

Message

Nícolas F. R. A. Prado March 13, 2023, 9:29 p.m. UTC
A couple commits to make the mt8192 sound driver not spam the console.


Nícolas F. R. A. Prado (2):
  ASoC: mt8192: Remove function name log messages
  ASoC: mt8192: Move spammy messages to debug level

 sound/soc/mediatek/mt8192/mt8192-afe-clk.c    |  4 ---
 sound/soc/mediatek/mt8192/mt8192-afe-pcm.c    |  6 +---
 sound/soc/mediatek/mt8192/mt8192-dai-tdm.c    | 28 +++++++++----------
 .../mt8192/mt8192-mt6359-rt1015-rt5682.c      | 12 ++++----
 4 files changed, 19 insertions(+), 31 deletions(-)

Comments

Mark Brown March 15, 2023, 1:19 p.m. UTC | #1
On Mon, 13 Mar 2023 17:29:05 -0400, Nícolas F. R. A. Prado wrote:
> A couple commits to make the mt8192 sound driver not spam the console.
> 
> 
> Nícolas F. R. A. Prado (2):
>   ASoC: mt8192: Remove function name log messages
>   ASoC: mt8192: Move spammy messages to debug level
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: mt8192: Remove function name log messages
      commit: f147ca85d6ecaf65106d1650f3c2e8afacbc833f
[2/2] ASoC: mt8192: Move spammy messages to debug level
      commit: 5f2a53c0687b151c2ecad19995108b40df76ba86

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