From: Chengming Zhou <chengming.zhou@linux.dev>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, ming.lei@redhat.com, tj@kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Chengming Zhou <zhouchengming@bytedance.com>
Subject: Re: [PATCH v2 4/4] blk-mq: delete unused completion_data in struct request
Date: Thu, 6 Jul 2023 22:31:09 +0800 [thread overview]
Message-ID: <9b2a1bdc-0180-2e57-2b79-ab5e9ec0cbe5@linux.dev> (raw)
In-Reply-To: <20230706130858.GD13089@lst.de>
On 2023/7/6 21:08, Christoph Hellwig wrote:
> Looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Although I'd order it first or even send it separately as it doesn't need
> any of the other changes.
Ok, will order it first in the next version.
I thought it's too minor to send a separate patch, so put it in this series.
Thanks.
prev parent reply other threads:[~2023-07-06 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 11:03 [PATCH v2 0/4] blk-mq: optimize the size of struct request chengming.zhou
2023-06-29 11:03 ` [PATCH v2 1/4] blk-mq: use percpu csd to remote complete instead of per-rq csd chengming.zhou
2023-07-05 15:01 ` Ming Lei
2023-07-06 13:07 ` Christoph Hellwig
2023-07-06 14:23 ` Chengming Zhou
2023-07-06 14:39 ` Christoph Hellwig
2023-06-29 11:03 ` [PATCH v2 2/4] blk-flush: count inflight flush_data requests chengming.zhou
2023-07-05 15:10 ` Ming Lei
2023-07-06 13:08 ` Christoph Hellwig
2023-06-29 11:03 ` [PATCH v2 3/4] blk-flush: reuse rq queuelist in flush state machine chengming.zhou
2023-07-06 13:08 ` Christoph Hellwig
2023-06-29 11:03 ` [PATCH v2 4/4] blk-mq: delete unused completion_data in struct request chengming.zhou
2023-07-06 13:08 ` Christoph Hellwig
2023-07-06 14:31 ` Chengming Zhou [this message]
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=9b2a1bdc-0180-2e57-2b79-ab5e9ec0cbe5@linux.dev \
--to=chengming.zhou@linux.dev \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=tj@kernel.org \
--cc=zhouchengming@bytedance.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.