[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <49a7c0b667abe23d95d67cf0cf7ea7e193d9f2a1.1709773065.git.len.brown@intel.com>
Date: Wed, 6 Mar 2024 20:05:41 -0500
From: Len Brown <lenb@...nel.org>
To: kbusch@...nel.org,
linux-nvme@...ts.infradead.org
Cc: maxg@...lanox.com,
axboe@...nel.dk,
hch@....de,
sagi@...mberg.me,
linux-kernel@...r.kernel.org,
Len Brown <len.brown@...el.com>
Subject: [PATCH 1/1] nvme: Use pr_dbg, not pr_info, when setting shutdown timeout
From: Len Brown <len.brown@...el.com>
Some words are alarming in routine kernel messages.
"timeout" is one of them...
Here NVME is routinely setting a timeout value,
rather than reporting that a timeout has occurred.
Assuming this message is actually useful to somebody somewhere,
let's make it DEBUG level...
Fixes: 1a3838d732ea ("nvme: modify the debug level for setting shutdown timeout")
Signed-off-by: Len Brown <len.brown@...el.com>
---
drivers/nvme/host/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 0a96362912ce..e361af1953a4 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -3205,7 +3205,7 @@ static int nvme_init_identify(struct nvme_ctrl *ctrl)
shutdown_timeout, 60);
if (ctrl->shutdown_timeout != shutdown_timeout)
- dev_info(ctrl->device,
+ dev_dbg(ctrl->device,
"Shutdown timeout set to %u seconds\n",
ctrl->shutdown_timeout);
} else
--
2.40.1
Powered by blists - more mailing lists