public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: "Kai Mäkisara" <Kai.Makisara@kolumbus.fi>,
	linux-scsi@vger.kernel.org, dgilbert@interlog.com
Cc: martin.petersen@oracle.com, James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH 1/4] scsi: scsi_debug: Fix two typos in command definitions
Date: Fri, 28 Feb 2025 14:36:16 +0000	[thread overview]
Message-ID: <73bd63fa-9ea9-47b3-b6bb-aa97d2a0680f@oracle.com> (raw)
In-Reply-To: <20250228124627.177873-2-Kai.Makisara@kolumbus.fi>

On 28/02/2025 12:46, Kai Mäkisara wrote:
> Fix two command definitions:
> - flags and service action reversed in SEND DIAGNOSTIC
> - ATOMIC WRITE missing opcode
> 
> Signed-off-by: Kai Mäkisara <Kai.Makisara@kolumbus.fi>
> ---
>   drivers/scsi/scsi_debug.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
> index 2208dcba346e..4bc0c8350b99 100644
> --- a/drivers/scsi/scsi_debug.c
> +++ b/drivers/scsi/scsi_debug.c
> @@ -817,7 +817,7 @@ static const struct opcode_info_t opcode_info_arr[SDEB_I_LAST_ELEM_P1 + 1] = {
>   	    {6,  0x1, 0, 0, 0, 0xc7, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0} },
>   	{0, 0, 0, F_INV_OP | FF_RESPOND, NULL, NULL, /* ATA_PT */
>   	    {0,  0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0} },
> -	{0, 0x1d, F_D_OUT, 0, NULL, NULL,	/* SEND DIAGNOSTIC */
> +	{0, 0x1d, 0, F_D_OUT, NULL, NULL,	/* SEND DIAGNOSTIC */
>   	    {6,  0xf7, 0, 0xff, 0xff, 0xc7, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0} },
>   	{0, 0x42, 0, F_D_OUT | FF_MEDIA_IO, resp_unmap, NULL, /* UNMAP */
>   	    {10,  0x1, 0, 0, 0, 0, 0x3f, 0xff, 0xff, 0xc7, 0, 0, 0, 0, 0, 0} },
> @@ -852,7 +852,7 @@ static const struct opcode_info_t opcode_info_arr[SDEB_I_LAST_ELEM_P1 + 1] = {
>   		{16,  0x0 /* SA */, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff,
>   		 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xbf, 0xc7} },
>   /* 32 */
> -	{0, 0x0, 0x0, F_D_OUT | FF_MEDIA_IO,
> +	{0, 0x9c, 0x0, F_D_OUT | FF_MEDIA_IO,

Any idea why we don't use values from scsi_proto.h for these, e.g. 
WRITE_ATOMIC_16 in this case?

>   	    resp_atomic_write, NULL, /* ATOMIC WRITE 16 */
>   		{16,  0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff,
>   		 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff} },


  reply	other threads:[~2025-02-28 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 12:46 [PATCH 0/4] scsi: scsi_debug: Changes to improve support for device types Kai Mäkisara
2025-02-28 12:46 ` [PATCH 1/4] scsi: scsi_debug: Fix two typos in command definitions Kai Mäkisara
2025-02-28 14:36   ` John Garry [this message]
2025-02-28 12:46 ` [PATCH 2/4] scsi: scsi_debug: Different command definitions for different device types Kai Mäkisara
2025-02-28 12:46 ` [PATCH 2/4] scsi: scsi_debug: Enable different " Kai Mäkisara
2025-02-28 13:04   ` "Kai Mäkisara (Kolumbus)"
2025-03-10  7:36   ` kernel test robot
2025-02-28 12:46 ` [PATCH 3/4] scsi: scsi_debug: Move some tape-specific commands to separate definitions Kai Mäkisara
2025-02-28 12:46 ` [PATCH 4/4] scsi: scsi_debug: Use scsi_device->type instead os sdebug_ptype where possible Kai Mäkisara

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=73bd63fa-9ea9-47b3-b6bb-aa97d2a0680f@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=dgilbert@interlog.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    /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