[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230512135224.GE32242@lst.de>
Date: Fri, 12 May 2023 15:52:24 +0200
From: "hch@....de" <hch@....de>
To: Jinyoung CHOI <j-young.choi@...sung.com>
Cc: "axboe@...nel.dk" <axboe@...nel.dk>,
"kbusch@...nel.org" <kbusch@...nel.org>, "hch@....de" <hch@....de>,
"sagi@...mberg.me" <sagi@...mberg.me>,
"jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"johannes.thumshirn@....com" <johannes.thumshirn@....com>,
"kch@...dia.com" <kch@...dia.com>,
"willy@...radead.org" <willy@...radead.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 08/14] scsi: add scsi_alloc_integrity_sgtables() for
integrity process
On Wed, May 10, 2023 at 05:56:07PM +0900, Jinyoung CHOI wrote:
> + if (WARN_ON_ONCE(!prot_sdb)) {
> + /*
> + * This can happen if someone (e.g. multipath)
> + * queues a command to a device on an adapter
> + * that does not support DIX.
> + */
> + return BLK_STS_IOERR;
Nit: expand the comment to take up all 80 characters now that you've
unindented it.
Powered by blists - more mailing lists