Message ID | 20190619171302.10146-1-chaitanya.kulkarni@wdc.com (mailing list archive) |
---|---|
Headers | show |
Series | block: improve print_req_error | expand |
On 6/19/19 11:12 AM, Chaitanya Kulkarni wrote: > Hi, > > This patch-series is based on the initial patch posted by > Christoph Hellwig <hch@lst.de>. While debugging the driver and block > layer this print message is very meaningful. Also, we centralize the > REQ_OP_XXX to the string conversion in the blk-core.c so that other > dependent subsystems can use this helper without having to duplicate > the code e.g. f2fs, blk-mq-debugfs.c. > > Please consider this for 5.3. Something is wonky here. For 5.2, I just merged: commit f9bc64a0f0f884036d76d71edeaafb994c5ceddf (origin/for-5.3/block) Author: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com> Date: Thu Jun 13 07:14:21 2019 -0700 block: use req_op() to maintain consistency and then you go and do something different for 5.3?
On 06/20/2019 12:35 AM, Jens Axboe wrote: > On 6/19/19 11:12 AM, Chaitanya Kulkarni wrote: >> Hi, >> >> This patch-series is based on the initial patch posted by >> Christoph Hellwig <hch@lst.de>. While debugging the driver and block >> layer this print message is very meaningful. Also, we centralize the >> REQ_OP_XXX to the string conversion in the blk-core.c so that other >> dependent subsystems can use this helper without having to duplicate >> the code e.g. f2fs, blk-mq-debugfs.c. >> >> Please consider this for 5.3. > > Something is wonky here. For 5.2, I just merged: > > commit f9bc64a0f0f884036d76d71edeaafb994c5ceddf (origin/for-5.3/block) > Author: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com> > Date: Thu Jun 13 07:14:21 2019 -0700 > > block: use req_op() to maintain consistency > > and then you go and do something different for 5.3? I miss something. I just sent a V5 with latest for-next:- https://www.spinics.net/lists/linux-block/msg41848.html Please let me know if issue still exists. >