From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 6/7] scsi: return blk_status_t from device handler ->prep_fn
Date: Fri, 09 Nov 2018 16:59:29 -0800 [thread overview]
Message-ID: <1541811569.10602.9.camel@acm.org> (raw)
In-Reply-To: <20181109134241.29346-7-hch@lst.de>
On Fri, 2018-11-09 at 14:42 +0100, Christoph Hellwig wrote:
> Remove the last use of the old BLKPREP_* values, which get converted
> to BLK_STS_* later anyway.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2018-11-10 0:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 13:42 remove the legacy BLKPREP_* values Christoph Hellwig
2018-11-09 13:42 ` [PATCH 1/7] ide: cleanup ->prep_rq calling convention Christoph Hellwig
2018-11-10 0:46 ` Bart Van Assche
2018-11-09 13:42 ` [PATCH 2/7] scsi: simplify scsi_prep_state_check Christoph Hellwig
2018-11-10 0:47 ` Bart Van Assche
2018-11-09 13:42 ` [PATCH 3/7] scsi: push blk_status_t up into scsi_setup_{fs,scsi}_cmnd Christoph Hellwig
2018-11-09 13:52 ` Johannes Thumshirn
2018-11-10 0:48 ` Bart Van Assche
2018-11-09 13:42 ` [PATCH 4/7] scsi: clean up error handling in scsi_init_io Christoph Hellwig
2018-11-09 13:53 ` Johannes Thumshirn
2018-11-10 0:52 ` Bart Van Assche
2018-11-09 13:42 ` [PATCH 5/7] scsi: return blk_status_t from scsi_init_io and ->init_command Christoph Hellwig
2018-11-09 13:58 ` Johannes Thumshirn
2018-11-10 0:56 ` Bart Van Assche
2018-11-10 0:57 ` Bart Van Assche
2018-11-09 13:42 ` [PATCH 6/7] scsi: return blk_status_t from device handler ->prep_fn Christoph Hellwig
2018-11-09 14:01 ` Johannes Thumshirn
2018-11-10 0:59 ` Bart Van Assche [this message]
2018-11-09 13:42 ` [PATCH 7/7] block: remove the BLKPREP_* values Christoph Hellwig
2018-11-09 14:01 ` Johannes Thumshirn
2018-11-10 0:59 ` Bart Van Assche
2018-11-09 15:51 ` remove the legacy " Jens Axboe
2018-11-10 15:17 ` Jens Axboe
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=1541811569.10602.9.camel@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.