From: "Theodore Ts'o" <tytso@mit.edu>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kemeng Shi <shikemeng@huaweicloud.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
jack@suse.cz, ojaswin@linux.ibm.com, ritesh.list@gmail.com
Subject: Re: [PATCH v3 0/5] Minor improvements and cleanups to ext4 mballoc
Date: Tue, 7 May 2024 19:03:52 -0400 [thread overview]
Message-ID: <171512302194.3602678.5608981738614745810.b4-ty@mit.edu> (raw)
In-Reply-To: <20240424061904.987525-1-shikemeng@huaweicloud.com>
On Wed, 24 Apr 2024 14:18:59 +0800, Kemeng Shi wrote:
> v2->v3:
> -Coleect RVB from Jan
> -Remove more unneeded "cr =" in comment
>
> v1->v2:
> -Collect RVB from Jan and Ojaswin
> -Rewrite changelog of "ext4: call ext4_mb_mark_free_simple to free
> continuous bits in found chunk"
> -Remove "cr =" in comment of criteria name as criteria name has CR_
> prfefix now.
> -Only open codeing repeated checks in next_linear_group
>
> [...]
Applied, thanks!
[1/5] ext4: keep "prefetch_grp" and "nr" consistent
commit: 9c97c34a998a01bc0cf970b1685456bc2ea16b64
[2/5] ext4: add test_mb_mark_used_cost to estimate cost of mb_mark_used
commit: d0b88624f81f272626c767f4b715f4b690fcbed2
[3/5] ext4: call ext4_mb_mark_free_simple to free continuous bits in found chunk
commit: d1a3924e43a35860ed7edaeec7f901a1ade2ac37
[4/5] ext4: use correct criteria name instead stale integer number in comment
commit: 2caffb6a277bb0f2a482a2eb824d012d5f45f4d0
[5/5] ext4: open coding repeated check in next_linear_group
commit: da5704eef7037a5bc84a56519729d93d10a0e0a0
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2024-05-07 23:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 6:18 [PATCH v3 0/5] Minor improvements and cleanups to ext4 mballoc Kemeng Shi
2024-04-24 6:19 ` [PATCH v3 1/5] ext4: keep "prefetch_grp" and "nr" consistent Kemeng Shi
2024-04-24 6:19 ` [PATCH v3 2/5] ext4: add test_mb_mark_used_cost to estimate cost of mb_mark_used Kemeng Shi
2024-04-24 6:19 ` [PATCH v3 3/5] ext4: call ext4_mb_mark_free_simple to free continuous bits in found chunk Kemeng Shi
2024-04-29 16:46 ` Jan Kara
2024-04-24 6:19 ` [PATCH v3 4/5] ext4: use correct criteria name instead stale integer number in comment Kemeng Shi
2024-04-24 20:13 ` Jan Kara
2024-04-24 6:19 ` [PATCH v3 5/5] ext4: open coding repeated check in next_linear_group Kemeng Shi
2024-05-07 23:03 ` Theodore Ts'o [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=171512302194.3602678.5608981738614745810.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=shikemeng@huaweicloud.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 read-only IMAP folder(s) and NNTP newsgroup(s).