From: "Theodore Tso" <tytso@mit.edu>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org,
Baokun Li <libaokun@linux.alibaba.com>,
Zhang Yi <yi.zhang@huawei.com>,
Ritesh Harjani <ritesh.list@gmail.com>
Subject: Re: [PATCH 0/3] ext4: Fix credit estimates for extent tree modifications
Date: Mon, 17 Aug 2026 19:31:46 -0400 [thread overview]
Message-ID: <aoOYvl2tsk1o6TR9@mit.edu> (raw)
In-Reply-To: <an66zNiouBCgpS9M@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>
On Fri, Aug 14, 2026 at 12:21:30PM -0500, Ojaswin Mujoo wrote:
>
> I just noticed that the RVBs were not picked in your ext4/dev branch. I
> think they got missed somehow.
Hmm, I see them on the dev branch:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/log/?h=dev
and they are on today's linux-next branch.
- Ted
prev parent reply other threads:[~2026-08-17 23:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 15:35 [PATCH 0/3] ext4: Fix credit estimates for extent tree modifications Jan Kara
2026-08-05 15:35 ` [PATCH 1/3] ext4: Teach ext4_meta_trans_blocks() about number of allocated extents Jan Kara
2026-08-06 18:09 ` Ojaswin Mujoo
2026-08-07 2:59 ` Zhang Yi
2026-08-07 5:59 ` Ojaswin Mujoo
2026-08-07 7:05 ` Zhang Yi
2026-08-07 7:28 ` Ojaswin Mujoo
2026-08-05 15:35 ` [PATCH 2/3] ext4: Fix transaction overflow during writeback Jan Kara
2026-08-07 3:36 ` Zhang Yi
2026-08-07 8:40 ` Ojaswin Mujoo
2026-08-05 15:35 ` [PATCH 3/3] ext4: Fix estimate extent index blocks in ext4_ext_index_trans_blocks() Jan Kara
2026-08-07 4:46 ` Zhang Yi
2026-08-07 6:37 ` Ojaswin Mujoo
2026-08-17 11:39 ` Jan Kara
2026-08-17 15:04 ` Ojaswin Mujoo
2026-08-10 1:33 ` [PATCH 0/3] ext4: Fix credit estimates for extent tree modifications Theodore Ts'o
2026-08-14 6:51 ` Ojaswin Mujoo
2026-08-17 23:31 ` Theodore Tso [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=aoOYvl2tsk1o6TR9@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=libaokun@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=yi.zhang@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.