From: "Theodore Ts'o" <tytso@mit.edu>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: Ritesh Harjani <ritesh.list@gmail.com>,
adilger.kernel@dilger.ca, ojaswin@linux.ibm.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 8/8] ext4: add first unit test for ext4_mb_new_blocks_simple in mballoc
Date: Fri, 18 Aug 2023 01:07:33 -0400 [thread overview]
Message-ID: <20230818050733.GH3464136@mit.edu> (raw)
In-Reply-To: <fa68f2a4-e8f1-8856-0a99-736b70de0c52@huaweicloud.com>
Hi, it sounds like you are planning on a few additional changes to
this patch series, right? When might you be planning on pushing out
the next version?
Thanks,
- Ted
next prev parent reply other threads:[~2023-08-18 5:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 14:39 [PATCH v5 0/8] cleanups and unit test for mballoc Kemeng Shi
2023-06-29 14:40 ` [PATCH v5 1/8] ext4: factor out codes to update block bitmap and group descriptor on disk from ext4_mb_mark_bb Kemeng Shi
2023-07-22 6:24 ` Ritesh Harjani
2023-07-25 3:40 ` Kemeng Shi
2023-06-29 14:40 ` [PATCH v5 2/8] ext4: call ext4_mb_mark_group_bb in ext4_free_blocks_simple Kemeng Shi
2023-06-29 14:40 ` [PATCH v5 3/8] ext4: extent ext4_mb_mark_group_bb to support allocation under journal Kemeng Shi
2023-06-29 14:40 ` [PATCH v5 4/8] ext4: call ext4_mb_mark_group_bb in ext4_mb_mark_diskspace_used Kemeng Shi
2023-06-29 14:40 ` [PATCH v5 5/8] ext4: call ext4_mb_mark_group_bb in ext4_mb_clear_bb Kemeng Shi
2023-07-22 15:04 ` Ritesh Harjani
2023-07-23 5:37 ` Ritesh Harjani
2023-07-25 8:21 ` Kemeng Shi
2023-06-29 14:40 ` [PATCH v5 6/8] ext4: call ext4_mb_mark_group_bb in ext4_group_add_blocks Kemeng Shi
2023-06-29 14:40 ` [PATCH v5 7/8] ext4: add some kunit stub for mballoc kunit test Kemeng Shi
2023-07-24 13:47 ` Jason Yan
2023-06-29 14:40 ` [PATCH v5 8/8] ext4: add first unit test for ext4_mb_new_blocks_simple in mballoc Kemeng Shi
2023-08-03 14:41 ` Ritesh Harjani
2023-08-07 1:46 ` Kemeng Shi
2023-08-18 5:07 ` Theodore Ts'o [this message]
2023-08-18 8:56 ` Kemeng Shi
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=20230818050733.GH3464136@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--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 NNTP newsgroup(s).