From: Jens Axboe <axboe@kernel.dk>
To: Chengming Zhou <zhouchengming@bytedance.com>, tj@kernel.org
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
duanxiongchun@bytedance.com, songmuchun@bytedance.com
Subject: Re: [PATCH] blk-iocos: fix inuse clamp when iocg deactivate or free
Date: Mon, 16 May 2022 11:40:51 -0600 [thread overview]
Message-ID: <83042952-30e9-849a-be31-c31e951e8d70@kernel.dk> (raw)
In-Reply-To: <bbd8744f-d938-c4a5-cb02-145c9875ea53@bytedance.com>
On 5/16/22 6:18 AM, Chengming Zhou wrote:
> Then this effect is very small, unlikely to have an impact in
> practice. Should I modify the commit message to send v2 or just drop
> it?
Send a v2 please.
--
Jens Axboe
next prev parent reply other threads:[~2022-05-16 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 10:19 [PATCH] blk-iocos: fix inuse clamp when iocg deactivate or free Chengming Zhou
2022-05-16 12:18 ` Chengming Zhou
2022-05-16 17:40 ` Jens Axboe [this message]
2022-05-16 18:37 ` Tejun Heo
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=83042952-30e9-849a-be31-c31e951e8d70@kernel.dk \
--to=axboe@kernel.dk \
--cc=duanxiongchun@bytedance.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songmuchun@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).