From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Mark Brown" <broonie@kernel.org>
Cc: kernel@collabora.com, Akihiko Odaki <akihiko.odaki@gmail.com>,
Jaroslav Kysela <perex@perex.cz>,
Jiaxin Yu <jiaxin.yu@mediatek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Takashi Iwai <tiwai@suse.com>, Tzung-Bi Shih <tzungbi@kernel.org>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/2] ASoC: mt8192: Move spammy messages to debug level
Date: Tue, 14 Mar 2023 09:30:17 +0100 [thread overview]
Message-ID: <61425c0f-a486-1503-042b-9327f414684d@collabora.com> (raw)
In-Reply-To: <20230313212908.2282961-3-nfraprado@collabora.com>
Il 13/03/23 22:29, Nícolas F. R. A. Prado ha scritto:
> There are many log messages throughout the mt8192 sound drivers that
> print to the info level and are triggered very frequently. Move these
> messages to the debug level to avoid spamming the console.
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2023-03-14 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 21:29 [PATCH 0/2] ASoC: mt8192: Address spammy log messages Nícolas F. R. A. Prado
2023-03-13 21:29 ` [PATCH 1/2] ASoC: mt8192: Remove function name " Nícolas F. R. A. Prado
2023-03-14 8:30 ` AngeloGioacchino Del Regno
2023-03-14 13:40 ` Nícolas F. R. A. Prado
2023-03-13 21:29 ` [PATCH 2/2] ASoC: mt8192: Move spammy messages to debug level Nícolas F. R. A. Prado
2023-03-14 8:30 ` AngeloGioacchino Del Regno [this message]
2023-03-15 13:19 ` [PATCH 0/2] ASoC: mt8192: Address spammy log messages Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61425c0f-a486-1503-042b-9327f414684d@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=akihiko.odaki@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jiaxin.yu@mediatek.com \
--cc=kernel@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tzungbi@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®