[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250227233110.36596-1-romank@linux.microsoft.com>
Date: Thu, 27 Feb 2025 15:31:10 -0800
From: Roman Kisel <romank@...ux.microsoft.com>
To: kys@...rosoft.com,
haiyangz@...rosoft.com,
wei.liu@...nel.org,
decui@...rosoft.com,
James.Bottomley@...senPartnership.com,
martin.petersen@...cle.com,
linux-hyperv@...r.kernel.org,
linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: apais@...rosoft.com,
benhill@...rosoft.com,
sunilmut@...rosoft.com
Subject: [PATCH hyperv-next] scsi: storvsc: Don't call the packet status the hypercall status
The log statement reports the packet status code as the hypercall
status code which causes confusion when debugging.
Fix the name of the datum being logged.
Signed-off-by: Roman Kisel <romank@...ux.microsoft.com>
---
drivers/scsi/storvsc_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c
index a8614e54544e..d7ec79536d9a 100644
--- a/drivers/scsi/storvsc_drv.c
+++ b/drivers/scsi/storvsc_drv.c
@@ -1183,7 +1183,7 @@ static void storvsc_on_io_completion(struct storvsc_device *stor_device,
STORVSC_LOGGING_WARN : STORVSC_LOGGING_ERROR;
storvsc_log_ratelimited(device, loglevel,
- "tag#%d cmd 0x%x status: scsi 0x%x srb 0x%x hv 0x%x\n",
+ "tag#%d cmd 0x%x status: scsi 0x%x srb 0x%x sts 0x%x\n",
scsi_cmd_to_rq(request->cmd)->tag,
stor_pkt->vm_srb.cdb[0],
vstor_packet->vm_srb.scsi_status,
--
2.43.0
Powered by blists - more mailing lists