From: "Darrick J. Wong" <djwong@kernel.org>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: chandan.babu@oracle.com, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] xfs: Remove unused function is_rt_data_fork
Date: Sun, 3 Mar 2024 18:44:45 -0800 [thread overview]
Message-ID: <20240304024445.GM1927156@frogsfrogsfrogs> (raw)
In-Reply-To: <20240304022408.111558-1-jiapeng.chong@linux.alibaba.com>
On Mon, Mar 04, 2024 at 10:24:08AM +0800, Jiapeng Chong wrote:
> The function are defined in the rmap_repair.c file, but not called
> elsewhere, so delete the unused function.
>
> fs/xfs/scrub/rmap_repair.c:436:1: warning: unused function 'is_rt_data_fork'.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=8425
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Oh hey, that really /is/ unused, even in djwong-wtf. Good catch!
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/scrub/rmap_repair.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/fs/xfs/scrub/rmap_repair.c b/fs/xfs/scrub/rmap_repair.c
> index e8e07b683eab..7e73ddfb3d44 100644
> --- a/fs/xfs/scrub/rmap_repair.c
> +++ b/fs/xfs/scrub/rmap_repair.c
> @@ -432,14 +432,6 @@ xrep_rmap_scan_iroot_btree(
> return error;
> }
>
> -static inline bool
> -is_rt_data_fork(
> - struct xfs_inode *ip,
> - int whichfork)
> -{
> - return XFS_IS_REALTIME_INODE(ip) && whichfork == XFS_DATA_FORK;
> -}
> -
> /*
> * Iterate the block mapping btree to collect rmap records for anything in this
> * fork that matches the AG. Sets @mappings_done to true if we've scanned the
> --
> 2.20.1.7.g153144c
>
>
prev parent reply other threads:[~2024-03-04 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 2:24 Jiapeng Chong
2024-03-04 2:44 ` 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=20240304024445.GM1927156@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=abaci@linux.alibaba.com \
--cc=chandan.babu@oracle.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®