From: Roman Kisel Sent: Friday, February 28, 2025
2:55 PM
>
> On 2/28/2025 12:55 PM, Michael Kelley wrote:
> > From: Roman Kisel Sent: Thursday, February 27,
> > 2025
> 3:31 PM
> >>
> >> The log statement reports the packet status code as the hypercall
> >> status code which causes confusion w
From: Roman Kisel Sent: Thursday, February 27,
2025 3:31 PM
>
> 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
> ---
> drivers/scsi/storvsc_drv.c
On 2/28/2025 12:55 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Thursday, February 27,
2025 3:31 PM
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
On 2/28/2025 12:21 PM, Easwar Hariharan wrote:
On 2/27/2025 3:31 PM, Roman Kisel wrote:
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
---
drivers/scsi
On 2/27/2025 3:31 PM, Roman Kisel wrote:
> 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
> ---
> drivers/scsi/storvsc_drv.c | 2 +-
> 1 file change
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
---
drivers/scsi/storvsc_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi
