From: Mario Limonciello <mario.limonciello@amd.com>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>, vkoul@kernel.org
Cc: alsa-devel@alsa-project.org, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.dev, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, venkataprasad.potturu@amd.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soundwire: amd: change the log level for command response log
Date: Tue, 18 Feb 2025 11:12:34 -0600 [thread overview]
Message-ID: <dbe31e75-15d0-4001-be0c-2babbd503a40@amd.com> (raw)
In-Reply-To: <20250218065924.917915-1-Vijendar.Mukunda@amd.com>
On 2/18/2025 00:59, Vijendar Mukunda wrote:
> Change log level for command response log to dev_dbg_ratelimited when
> command is ignored.
>
> Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/soundwire/amd_manager.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/soundwire/amd_manager.c b/drivers/soundwire/amd_manager.c
> index dcf85f94950a..a12c68b93b1c 100644
> --- a/drivers/soundwire/amd_manager.c
> +++ b/drivers/soundwire/amd_manager.c
> @@ -346,7 +346,7 @@ static enum sdw_command_response amd_sdw_fill_msg_resp(struct amd_sdw_manager *a
> msg->dev_num);
> return SDW_CMD_FAIL;
> }
> - dev_err_ratelimited(amd_manager->dev, "command is ignored for Slave %d\n",
> + dev_dbg_ratelimited(amd_manager->dev, "command is ignored for Slave %d\n",
> msg->dev_num);
> return SDW_CMD_IGNORED;
> }
next prev parent reply other threads:[~2025-02-18 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 6:59 [PATCH] soundwire: amd: change the log level for command response log Vijendar Mukunda
2025-02-18 17:12 ` Mario Limonciello [this message]
2025-02-27 7:01 ` Vinod Koul
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=dbe31e75-15d0-4001-be0c-2babbd503a40@amd.com \
--to=mario.limonciello@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=venkataprasad.potturu@amd.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.com \
/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