Re: [PATCH 17/34] stex: do not set COMMAND_COMPLETE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Hannes Reinecke <hare@xxxxxxx>
Subject: Re: [PATCH 17/34] stex: do not set COMMAND_COMPLETE
From: Christoph Hellwig <hch@xxxxxx>
Date: Wed, 2 Dec 2020 17:32:15 +0100
Cc: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>, James Bottomley <james.bottomley@xxxxxxxxxxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, linux-scsi@xxxxxxxxxxxxxxx
In-reply-to: <20201202115249.37690-18-hare@suse.de>
User-agent: Mutt/1.5.17 (2007-11-01)

On Wed, Dec 02, 2020 at 12:52:32PM +0100, Hannes Reinecke wrote:
> COMMAND_COMPLETE is defined as '0', so setting it is quite pointless.

Looks good,

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- [PATCH 00/34] SCSI result handling cleanup, part 1
  - From: Hannes Reinecke
- [PATCH 17/34] stex: do not set COMMAND_COMPLETE
  - From: Hannes Reinecke

Prev by Date: Re: [PATCH 16/34] hpsa: do not set COMMAND_COMPLETE
Next by Date: Re: [PATCH 18/34] nsp_cs: drop internal SCSI message definition
Previous by thread: [PATCH 17/34] stex: do not set COMMAND_COMPLETE
Next by thread: [PATCH 12/34] dc395: drop private SAM status code definitions
Index(es):
- Date
- Thread

[Index of Archives] [SCSI Target Devel] [Linux SCSI Target Infrastructure] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Linux IIO] [Samba] [Device Mapper]

Powered by Linux