From: Eric Blake <eblake@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Paolo Bonzini <pbonzini@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [RFC PATCH 1/2] scsi/utils: Add INVALID_PARAM_VALUE sense code definition
Date: Wed, 20 Jan 2021 08:58:28 -0600 [thread overview]
Message-ID: <505a6e2f-a07b-5e1f-a6d0-3d32b6388bb3@redhat.com> (raw)
In-Reply-To: <20210118170308.282442-2-philmd@redhat.com>
On 1/18/21 11:03 AM, Philippe Mathieu-Daudé wrote:
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> include/scsi/utils.h | 2 ++
> scsi/utils.c | 5 +++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/include/scsi/utils.h b/include/scsi/utils.h
> index fbc55882799..096489c6cd1 100644
> --- a/include/scsi/utils.h
> +++ b/include/scsi/utils.h
> @@ -57,6 +57,8 @@ extern const struct SCSISense sense_code_LBA_OUT_OF_RANGE;
> extern const struct SCSISense sense_code_INVALID_FIELD;
> /* Illegal request, Invalid field in parameter list */
> extern const struct SCSISense sense_code_INVALID_PARAM;
> +/* Illegal request, Invalid value in parameter list */
> +extern const struct SCSISense sense_code_INVALID_PARAM_VALUE;
> /* Illegal request, Parameter list length error */
> extern const struct SCSISense sense_code_INVALID_PARAM_LEN;
> /* Illegal request, LUN not supported */
Pre-existing: the term 'illegal' is suspect in computer science (the
code isn't breaking any laws); I prefer 'invalid'. But that's a pet
peeve of mine, and not something you need to change here.
> diff --git a/scsi/utils.c b/scsi/utils.c
> index b37c2830148..793c3a6b9c9 100644
> --- a/scsi/utils.c
> +++ b/scsi/utils.c
> @@ -197,6 +197,11 @@ const struct SCSISense sense_code_INVALID_PARAM = {
> .key = ILLEGAL_REQUEST, .asc = 0x26, .ascq = 0x00
> };
>
> +/* Illegal request, Invalid value in parameter list */
> +const struct SCSISense sense_code_INVALID_PARAM_VALUE = {
> + .key = ILLEGAL_REQUEST, .asc = 0x26, .ascq = 0x01
> +};
> +
> /* Illegal request, Parameter list length error */
> const struct SCSISense sense_code_INVALID_PARAM_LEN = {
> .key = ILLEGAL_REQUEST, .asc = 0x1a, .ascq = 0x00
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-01-20 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 17:03 [RFC PATCH 0/2] hw/usb/dev-uas: Fix Clang 11 -Wgnu-variable-sized-type-not-at-end error Philippe Mathieu-Daudé
2021-01-18 17:03 ` [RFC PATCH 1/2] scsi/utils: Add INVALID_PARAM_VALUE sense code definition Philippe Mathieu-Daudé
2021-01-20 14:58 ` Eric Blake [this message]
2021-01-20 16:01 ` Gerd Hoffmann
2021-01-20 16:04 ` Philippe Mathieu-Daudé
2021-01-18 17:03 ` [RFC PATCH 2/2] hw/usb/dev-uas: Report command additional adb length as unsupported Philippe Mathieu-Daudé
2021-01-19 23:28 ` Philippe Mathieu-Daudé
2021-01-20 14:11 ` Eric Blake
2021-01-19 16:41 ` [RFC PATCH 0/2] hw/usb/dev-uas: Fix Clang 11 -Wgnu-variable-sized-type-not-at-end error Gerd Hoffmann
2021-01-19 16:49 ` Philippe Mathieu-Daudé
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=505a6e2f-a07b-5e1f-a6d0-3d32b6388bb3@redhat.com \
--to=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).