From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 22 Jan 2018 08:32:42 -0800 From: Christoph Hellwig To: Ming Lei Cc: Jens Axboe , linux-block@vger.kernel.org, Christoph Hellwig , Mike Snitzer , dm-devel@redhat.com, Laurence Oberman , Bart Van Assche , "James E . J . Bottomley" , "Martin K . Petersen" , linux-scsi@vger.kernel.org Subject: Re: [PATCH 1/5] blk-mq: introduce BLK_STS_DEV_RESOURCE Message-ID: <20180122163242.GB23984@infradead.org> References: <20180122033550.27855-1-ming.lei@redhat.com> <20180122033550.27855-2-ming.lei@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20180122033550.27855-2-ming.lei@redhat.com> List-ID: > - if (ret == BLK_STS_RESOURCE) { > + if ((ret == BLK_STS_RESOURCE) || (ret == BLK_STS_DEV_RESOURCE)) { No need for the inner braces here. > + if ((ret == BLK_STS_RESOURCE) || (ret == BLK_STS_DEV_RESOURCE)) Same here. > +/* > + * This status is returned from driver to block layer if device related > + * resource is run out of, but driver can guarantee that IO dispatch is > + * triggered in future when the resource is available. > + */ > +#define BLK_STS_DEV_RESOURCE ((__force blk_status_t)13) We'll need some good explanation on BLK_STS_RESOURCE vs BLK_STS_DEV_RESOURCE I think. Except for these nitpicks this looks fine to me.