From: Carlos Maiolino <cem@kernel.org>
To: Zizhi Wo <wozizhi@huaweicloud.com>
Cc: dgc@kernel.org, djwong@kernel.org, hch@lst.de,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
yangerkun@huawei.com, chengzhihao1@huawei.com,
wozizhi@huawei.com
Subject: Re: [PATCH 0/5] xfs: remove leftover dead declarations in headers
Date: Fri, 4 Sep 2026 17:24:33 +0200 [thread overview]
Message-ID: <aprh7OnJPCL-iIIK@andromeda.toxiclabs.cc> (raw)
In-Reply-To: <20260904060648.1966130-1-wozizhi@huaweicloud.com>
On Fri, Sep 04, 2026 at 02:06:43PM +0800, Zizhi Wo wrote:
> While reading the XFS log code I noticed that the implementation of
> xlog_assign_tail_lsn() had already been removed, but its declaration was
> left behind in the header. Such orphaned declarations (implementation gone,
> no callers) can simply be dropped.
>
> Suspecting more of these existed, I scanned the XFS headers (using GLM-5.2
> to help, then verified each by hand) and this series removes the leftover
> declarations I could confirm. Some of these have been stale for a long time
> -- the oldest dates back to 2006.
>
> Note that scrub still has a fair number of functions that do have
> implementations but no callers (e.g. xchk_process_rt_error). I'm not sure
> removing those is appropriate, since they may be intended for future use,
> so they are not touched here.
>
> Cleanup only, no functional change.
>
> Zizhi Wo (5):
> xfs: remove unused xlog_assign_tail_lsn declarations
> xfs: remove unused xfs_iext_realloc declaration
> xfs: remove unused xfs_buf_iodone declaration
> xfs: remove unused kmem_to_page helper
> xfs: remove never-implemented scrub declarations
Honestly this all could have been a single patch, I don't believe the
'when the last user was gone' matters at least for me as I could find if
through a quick `git log` scan. Darrick was fine with it so I won't
enforce it to be a single cleanup patch.
At least get rid of the "Assisted-By: <model>" thing and send a new
version as we don't accept models discrimination anymore.
Carlos
>
> fs/xfs/scrub/common.h | 1 -
> fs/xfs/scrub/scrub.h | 1 -
> fs/xfs/scrub/tempfile.h | 4 ----
> fs/xfs/xfs_buf_item.h | 1 -
> fs/xfs/xfs_inode.h | 1 -
> fs/xfs/xfs_log.h | 2 --
> fs/xfs/xfs_platform.h | 11 -----------
> 7 files changed, 21 deletions(-)
>
> --
> 2.52.0
>
>
next prev parent reply other threads:[~2026-09-04 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 6:06 Zizhi Wo
2026-09-04 6:06 ` [PATCH 1/5] xfs: remove unused xlog_assign_tail_lsn declarations Zizhi Wo
2026-09-04 6:06 ` [PATCH 2/5] xfs: remove unused xfs_iext_realloc declaration Zizhi Wo
2026-09-04 6:06 ` [PATCH 3/5] xfs: remove unused xfs_buf_iodone declaration Zizhi Wo
2026-09-04 6:06 ` [PATCH 4/5] xfs: remove unused kmem_to_page helper Zizhi Wo
2026-09-04 6:06 ` [PATCH 5/5] xfs: remove never-implemented scrub declarations Zizhi Wo
2026-09-04 6:24 ` [PATCH 0/5] xfs: remove leftover dead declarations in headers Darrick J. Wong
2026-09-04 15:24 ` Carlos Maiolino [this message]
2026-09-05 0:24 ` Zizhi Wo
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=aprh7OnJPCL-iIIK@andromeda.toxiclabs.cc \
--to=cem@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=dgc@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=wozizhi@huawei.com \
--cc=wozizhi@huaweicloud.com \
--cc=yangerkun@huawei.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
all inboxes | Powered by JetHome®