From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next updated to e965895c8872
Date: Thu, 10 Sep 2026 11:11:11 +0200 [thread overview]
Message-ID: <aqJzuukCHRxPzFxO@andromeda.toxiclabs.cc> (raw)
Hi folks,
The for-next branch of the xfs-linux repository at:
gitolite.kernel.org:/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update.
The new head of the for-next branch is commit:
e965895c8872 Merge branch 'xfs-7.3-fixes' into for-next
9 new commits:
Carlos Maiolino (1):
[e965895c8872] Merge branch 'xfs-7.3-fixes' into for-next
Darrick J. Wong (6):
[2c67526f55f3] xfs: snapshot scrub stats when rendering them
[c7de6c2cefd2] xfs: report healthy filesystem events in scrub stats
[45125e769b6a] xfs: report runtime failures in scrub
[08655d4168c8] xfs: remove redundant function declaration
[036c497d345e] xfs: snapshot old AGFL before rewriting it
[763490d70e9b] xfs: bail out on bitmap errors in xrep_agfl_fill
Deepanshu Kartikey (1):
[4870da4f49ae] xfs: take hm->lock in xfs_ioc_health_monitor() before insert
Zizhi Wo (1):
[157dcb8230a4] xfs: remove several unused and never-implemented declarations
Code Diffstat:
fs/xfs/scrub/agheader_repair.c | 39 +++++++++++++++++++++++++-----------
fs/xfs/scrub/common.h | 1 -
fs/xfs/scrub/dabtree.h | 2 --
fs/xfs/scrub/scrub.h | 1 -
fs/xfs/scrub/stats.c | 45 +++++++++++++++++++++++++++---------------
fs/xfs/scrub/tempfile.h | 4 ----
fs/xfs/xfs_buf_item.h | 1 -
fs/xfs/xfs_healthmon.c | 2 ++
fs/xfs/xfs_inode.h | 1 -
fs/xfs/xfs_log.h | 2 --
10 files changed, 59 insertions(+), 39 deletions(-)
reply other threads:[~2026-09-10 9:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aqJzuukCHRxPzFxO@andromeda.toxiclabs.cc \
--to=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