Hi Johannes, Thanks for you kindly comment. On Mon, 2018-07-02 at 10:15 +0200, Johannes Thumshirn wrote: > On Sun, Jul 01, 2018 at 01:21:39AM +0900, Minwoo Im wrote: > > > > set->mq_map is now currently cleared if something goes wrong when > > establishing a queue map in blk-mq-pci.c. It's also cleared before > > updating a queue map in blk_mq_update_queue_map(). > > > > This patch provides an API to clear set->mq_map to make it clear. > Is there a follow up patch to this which justifies the change? > > With no 2nd consumer of the function I fear this will be disregarded > as useless code churn. No 2nd follow-up patch will be there. I thought these two parts are using a same unit-function to clear the set->mq-map. Also thought it would be great for the future use when it needs to be cleared. However, as you mentioned, I totally agree with your point. It seems just churns for churns' sake with no more usage for now. Thanks for your comment, again. Minwoo Im > > Byte, > Johannes
