From: Bill O'Donnell <bodonnel@redhat.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: chandan.babu@oracle.com, djwong@kernel.org,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] xfs: Remove unused function
Date: Tue, 7 Nov 2023 13:26:46 -0600 [thread overview]
Message-ID: <ZUqPdhc4RQxL8TVB@redhat.com> (raw)
In-Reply-To: <20231103073040.649-1-jiapeng.chong@linux.alibaba.com>
On Fri, Nov 03, 2023 at 03:30:40PM +0800, Jiapeng Chong wrote:
> The function are defined in the bitmap.c file, but not called
> elsewhere, so delete the unused function.
>
> fs/xfs/scrub/bitmap.c:55:1: warning: unused function 'xbitmap_tree_iter_next'.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=7137
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Makes sense.
Reviewed-by: Bill O'Donnell <bodonnel@redhat.com>
> ---
> fs/xfs/scrub/bitmap.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/fs/xfs/scrub/bitmap.c b/fs/xfs/scrub/bitmap.c
> index e0c89a9a0ca0..ba4b18e40faa 100644
> --- a/fs/xfs/scrub/bitmap.c
> +++ b/fs/xfs/scrub/bitmap.c
> @@ -48,10 +48,6 @@ static inline struct xbitmap_node *
> xbitmap_tree_iter_first(struct rb_root_cached *root, uint64_t start,
> uint64_t last);
>
> -static inline struct xbitmap_node *
> -xbitmap_tree_iter_next(struct xbitmap_node *node, uint64_t start,
> - uint64_t last);
> -
> INTERVAL_TREE_DEFINE(struct xbitmap_node, bn_rbnode, uint64_t,
> __bn_subtree_last, START, LAST, static inline, xbitmap_tree)
>
> --
> 2.20.1.7.g153144c
>
next prev parent reply other threads:[~2023-11-07 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 7:30 [PATCH] xfs: Remove unused function Jiapeng Chong
2023-11-07 19:26 ` Bill O'Donnell [this message]
2023-11-07 20:44 ` Darrick J. Wong
2023-11-11 15:39 ` Eric Sandeen
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=ZUqPdhc4RQxL8TVB@redhat.com \
--to=bodonnel@redhat.com \
--cc=abaci@linux.alibaba.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--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 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.