From: Josef Bacik <josef@toxicpanda.com>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: update comment for reservation of metadata space for delayed items
Date: Mon, 28 Aug 2023 09:27:16 -0400 [thread overview]
Message-ID: <20230828132716.GC875235@perftesting> (raw)
In-Reply-To: <283a7c5087a950342a862fba42922fad4fc71365.1693208275.git.fdmanana@suse.com>
On Mon, Aug 28, 2023 at 08:38:36AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> The second comment at btrfs_delayed_item_reserve_metadata() refers to a
> field named "index_items_size" of a delayed inode, however that field
> does not exists - it existed in a previous patch version, but then it
> split into the fields "curr_index_batch_size" and "index_item_leaves"
> in the final patch version that was picked. So update the comment.
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2023-08-28 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 7:38 [PATCH] btrfs: update comment for reservation of metadata space for delayed items fdmanana
2023-08-28 13:27 ` Josef Bacik [this message]
2023-09-05 11:06 ` David Sterba
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=20230828132716.GC875235@perftesting \
--to=josef@toxicpanda.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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