All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] blk-mq: code clean-up by adding an API to clear set->mq_map
Date: Mon, 02 Jul 2018 21:55:57 +0900	[thread overview]
Message-ID: <1530536157.13674.4.camel@gmail.com> (raw)
In-Reply-To: <20180702081539.z5rj6wfh6v4zz6bv@linux-x5ow.site>

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

  reply	other threads:[~2018-07-02 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 16:21 [PATCH] blk-mq: code clean-up by adding an API to clear set->mq_map Minwoo Im
2018-07-02  8:15 ` Johannes Thumshirn
2018-07-02 12:55   ` Minwoo Im [this message]
2018-07-02 13:02     ` Johannes Thumshirn
2018-07-02 13:20       ` Minwoo Im
2018-07-02 13:27         ` Johannes Thumshirn
2018-07-02 13:34           ` Minwoo Im
2018-07-02 13:41             ` Johannes Thumshirn

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=1530536157.13674.4.camel@gmail.com \
    --to=minwoo.im.dev@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=jthumshirn@suse.de \
    --cc=linux-block@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.