From: Jens Axboe <axboe@kernel.dk>
To: hch@lst.de, jack@suse.cz, Tang Yizhou <yizhou.tang@shopee.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
tangyeechou@gmail.com
Subject: Re: [PATCH v3 0/3] Optimize wbt and update its comments and doc
Date: Mon, 11 Aug 2025 10:21:57 -0600 [thread overview]
Message-ID: <175492931717.714692.13410561974179783344.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250727173959.160835-1-yizhou.tang@shopee.com>
On Mon, 28 Jul 2025 01:39:56 +0800, Tang Yizhou wrote:
> Some minor optimizations and updates of comments and doc for wbt.
>
> v3:
> Fix a typo: change 'cur_win_nsec' to 'curr_win_nsec'.
>
> v2:
> Patch #1: Pick up Jan and Kuai's Reviewed-by tag.
> Patch #2: Pick up Jan's Reviewed-by tag.
> Patch #3: Take Jan and Kuai's advice. Change the name to
> 'curr_win_nsec'.
>
> [...]
Applied, thanks!
[1/3] blk-wbt: Optimize wbt_done() for non-throttled writes
commit: d8b96a79622e03813c221450498ca9742704ebf2
[2/3] blk-wbt: Eliminate ambiguity in the comments of struct rq_wb
commit: bccdfcd56d4b5b78d0d76f46d0e89a51330dfd75
[3/3] blk-wbt: doc: Update the doc of the wbt_lat_usec interface
commit: 0452f08395f8e7d04fe3744443dad396b3330d0c
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-08-11 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 17:39 Tang Yizhou
2025-07-27 17:39 ` [PATCH v3 1/3] blk-wbt: Optimize wbt_done() for non-throttled writes Tang Yizhou
2025-07-27 17:39 ` [PATCH v3 2/3] blk-wbt: Eliminate ambiguity in the comments of struct rq_wb Tang Yizhou
2025-07-27 17:39 ` [PATCH v3 3/3] blk-wbt: doc: Update the doc of the wbt_lat_usec interface Tang Yizhou
2025-07-28 1:28 ` Yu Kuai
2025-07-28 9:41 ` Jan Kara
2025-08-04 16:46 ` [PATCH v3 0/3] Optimize wbt and update its comments and doc Yizhou Tang
2025-08-11 16:21 ` Jens Axboe [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=175492931717.714692.13410561974179783344.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tangyeechou@gmail.com \
--cc=yizhou.tang@shopee.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
all inboxes | Powered by JetHome®