From: Roman Kisel <romank@linux.microsoft.com>
To: eahariha@linux.microsoft.com, mhklinux@outlook.com,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, linux-hyperv@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: apais@microsoft.com, benhill@microsoft.com, sunilmut@microsoft.com
Subject: [PATCH hyperv-next v2 0/1] scsi: storvsc: Don't report the host packet status as the hv status
Date: Mon, 3 Mar 2025 16:09:39 -0800 [thread overview]
Message-ID: <20250304000940.9557-1-romank@linux.microsoft.com> (raw)
The patch includes fixes for the log statements that are ambigious as
to what they are logging.
Michael Kelley provided a great insight into the history of the code
(** Thank you, Michael! **) and tagged the V1 patch with "Reviewed-by".
I am not keeping the tag as a I added one more change to convert the
status code to hex in addition to what was approved.
[V2]
- Use "host" instead of opaque "sts".
** Thank you, Easwar! **
- Convert the status to hex everywhere.
[V1]: https://lore.kernel.org/linux-hyperv/20250227233110.36596-1-romank@linux.microsoft.com/
Roman Kisel (1):
scsi: storvsc: Don't report the host packet status as the hv status
drivers/scsi/storvsc_drv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
base-commit: 3a7f7785eae7cf012af128ca9e383c91e4955354
--
2.43.0
next reply other threads:[~2025-03-04 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 0:09 Roman Kisel [this message]
2025-03-04 0:09 ` [PATCH hyperv-next v2 1/1] scsi: storvsc: Don't report the host packet status as the hv status Roman Kisel
2025-03-04 4:06 ` Easwar Hariharan
2025-03-04 4:21 ` Michael Kelley
2025-03-11 1:19 ` Martin K. Petersen
2025-03-18 0:54 ` [PATCH hyperv-next v2 0/1] " Martin K. Petersen
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=20250304000940.9557-1-romank@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=apais@microsoft.com \
--cc=benhill@microsoft.com \
--cc=decui@microsoft.com \
--cc=eahariha@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mhklinux@outlook.com \
--cc=sunilmut@microsoft.com \
--cc=wei.liu@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;
as well as URLs for NNTP newsgroup(s).