From: Christoph Hellwig <hch@lst.de>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: axboe@kernel.dk, sagi@grimberg.me, yi.zhang@huawei.com,
yangerkun@huawei.com, snitzer@kernel.org,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, guz.fnst@cn.fujitsu.com,
dm-devel@redhat.com, kbusch@kernel.org, yukuai3@huawei.com,
hch@lst.de, agk@redhat.com
Subject: Re: [dm-devel] [PATCH -next RFC] block: count 'ios' and 'sectors' when io is done for bio-based device
Date: Wed, 15 Mar 2023 16:10:53 +0100 [thread overview]
Message-ID: <20230315151053.GA32066@lst.de> (raw)
In-Reply-To: <20230223091226.1135678-1-yukuai1@huaweicloud.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: axboe@kernel.dk, agk@redhat.com, snitzer@kernel.org,
dm-devel@redhat.com, kbusch@kernel.org, hch@lst.de,
sagi@grimberg.me, guz.fnst@cn.fujitsu.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, yukuai3@huawei.com,
yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH -next RFC] block: count 'ios' and 'sectors' when io is done for bio-based device
Date: Wed, 15 Mar 2023 16:10:53 +0100 [thread overview]
Message-ID: <20230315151053.GA32066@lst.de> (raw)
In-Reply-To: <20230223091226.1135678-1-yukuai1@huaweicloud.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2023-03-15 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 9:12 [dm-devel] [PATCH -next RFC] block: count 'ios' and 'sectors' when io is done for bio-based device Yu Kuai
2023-02-23 9:12 ` Yu Kuai
2023-02-28 1:01 ` [dm-devel] " Yu Kuai
2023-02-28 1:01 ` Yu Kuai
2023-03-07 10:44 ` [dm-devel] " Yu Kuai
2023-03-07 10:44 ` Yu Kuai
2023-03-15 15:10 ` Christoph Hellwig [this message]
2023-03-15 15:10 ` Christoph Hellwig
2023-03-15 15:25 ` [dm-devel] " Jens Axboe
2023-03-15 15:25 ` Jens Axboe
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=20230315151053.GA32066@lst.de \
--to=hch@lst.de \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=snitzer@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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.