From: David Sterba <dsterba@suse.cz>
To: Sun YangKai <sunk67188@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: simplify btrfs_lookup_inode_extref() by removing unused parameters
Date: Thu, 19 Jun 2025 15:33:41 +0200 [thread overview]
Message-ID: <20250619133341.GL4037@twin.jikos.cz> (raw)
In-Reply-To: <20250614033920.3874-1-sunk67188@gmail.com>
On Sat, Jun 14, 2025 at 11:39:06AM +0800, Sun YangKai wrote:
> The `btrfs_lookup_inode_extref()` function no longer requires transaction
> handle, insert length, or COW flag, as the onlycaller now perform a
> read-only lookup using `trans = NULL`, `ins_len = 0`, and `cow = 0`.
>
> This patch removes the unused parameters from the function signature and
> call sites, simplifying the interface and clarifying its current usage as
> a read-only lookup helper.
>
> No functional changes intended.
>
> Signed-off-by: Sun YangKai <sunk67188@gmail.com>
Added to for-next with some minor style adjustments, thanks.
prev parent reply other threads:[~2025-06-19 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 3:39 [PATCH] btrfs: simplify btrfs_lookup_inode_extref() by removing unused parameters Sun YangKai
2025-06-14 7:34 ` Qu Wenruo
2025-06-19 13:33 ` David Sterba [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=20250619133341.GL4037@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sunk67188@gmail.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