From: "Darrick J. Wong" <djwong@kernel.org>
To: Anuj Gupta <anuj1072538@gmail.com>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org,
Anuj Gupta <anuj20.g@samsung.com>
Subject: Re: [PATCH] xfs: remove unused xfs_reflink_remap_range declaration
Date: Fri, 4 Sep 2026 18:11:34 -0700 [thread overview]
Message-ID: <20260905011134.GH1933798@frogsfrogsfrogs> (raw)
In-Reply-To: <20260904123641.3028007-1-anuj1072538@gmail.com>
On Fri, Sep 04, 2026 at 06:06:41PM +0530, Anuj Gupta wrote:
> From: Anuj Gupta <anuj20.g@samsung.com>
>
> The implementation was inlined into xfs_file_remap_range() by commit
> 3fc9f5e40931 ("xfs: remove xfs_reflink_remap_range"), leaving this
> declaration orphaned.
>
> Signed-off-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_reflink.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/fs/xfs/xfs_reflink.h b/fs/xfs/xfs_reflink.h
> index 9d1ed9bb0bee..683c1841e640 100644
> --- a/fs/xfs/xfs_reflink.h
> +++ b/fs/xfs/xfs_reflink.h
> @@ -48,9 +48,6 @@ extern int xfs_reflink_end_cow(struct xfs_inode *ip, xfs_off_t offset,
> int xfs_reflink_end_atomic_cow(struct xfs_inode *ip, xfs_off_t offset,
> xfs_off_t count);
> extern int xfs_reflink_recover_cow(struct xfs_mount *mp);
> -extern loff_t xfs_reflink_remap_range(struct file *file_in, loff_t pos_in,
> - struct file *file_out, loff_t pos_out, loff_t len,
> - unsigned int remap_flags);
> extern int xfs_reflink_inode_has_shared_extents(struct xfs_trans *tp,
> struct xfs_inode *ip, bool *has_shared);
> extern int xfs_reflink_clear_inode_flag(struct xfs_inode *ip,
> --
> 2.43.0
>
>
prev parent reply other threads:[~2026-09-05 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 12:36 [PATCH] xfs: remove unused xfs_reflink_remap_range declaration Anuj Gupta
2026-09-05 1:11 ` Darrick J. Wong [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=20260905011134.GH1933798@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=anuj1072538@gmail.com \
--cc=anuj20.g@samsung.com \
--cc=cem@kernel.org \
--cc=linux-xfs@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