All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: axboe@kernel.dk, tom.leiming@gmail.com, bvanassche@acm.org,
	linux-block@vger.kernel.org
Subject: Re: [PATCH v5 5/5] block: rename blk_mq_alloc_rq_maps
Date: Wed, 6 May 2020 23:11:54 -0700	[thread overview]
Message-ID: <20200507061154.GD23530@infradead.org> (raw)
In-Reply-To: <4902af28b38221ade08940845306c57b5b8f371b.1588660550.git.zhangweiping@didiglobal.com>

On Tue, May 05, 2020 at 02:46:07PM +0800, Weiping Zhang wrote:
> rename blk_mq_alloc_rq_maps to blk_mq_alloc_map_and_requests,
> this function allocs both map and request, make function name align
> with funtion.
> 
> Reviewed-by: Ming Lei <ming.lei@redhat.com>
> Signed-off-by: Weiping Zhang <zhangweiping@didiglobal.com>

Looks good,

Reviewed-by: Christoph Hellwig <hch@lst.de>

  reply	other threads:[~2020-05-07  6:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05  6:43 [PATCH v5 0/5] Fix potential kernel panic when increase hardware queue Weiping Zhang
2020-05-05  6:43 ` [PATCH v5 1/5] block: free both rq_map and request Weiping Zhang
2020-05-07  6:10   ` Christoph Hellwig
2020-05-05  6:43 ` [PATCH v5 2/5] block: save previous hardware queue count before udpate Weiping Zhang
2020-05-07  6:11   ` Christoph Hellwig
2020-05-05  6:45 ` [PATCH v5 4/5] block: rename __blk_mq_alloc_rq_map Weiping Zhang
2020-05-07  6:11   ` Christoph Hellwig
2020-05-07 12:59     ` Weiping Zhang
2020-05-05  6:46 ` [PATCH v5 5/5] block: rename blk_mq_alloc_rq_maps Weiping Zhang
2020-05-07  6:11   ` Christoph Hellwig [this message]
2020-05-05  7:02 ` [PATCH v5 3/5] block: alloc map and request for new hardware queue Weiping Zhang
2020-05-05  7:38   ` [RESEND PATCH " Weiping Zhang
2020-05-07  6:13   ` [PATCH " Christoph Hellwig

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=20200507061154.GD23530@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=linux-block@vger.kernel.org \
    --cc=tom.leiming@gmail.com \
    /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.