[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <aW9wHq0fs8KpLCyj@sirena.org.uk>
Date: Tue, 20 Jan 2026 12:07:58 +0000
From: Mark Brown <broonie@...nel.org>
To: David Sterba <dsterba@...e.cz>, Boris Burkov <boris@....io>,
Johannes Thumshirn <johannes.thumshirn@....com>,
Qu Wenruo <wqu@...e.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build failure after merge of the btrfs-fixes tree
Hi all,
After merging the btrfs-fixes tree, today's linux-next build
(arm64 defconfig) failed like this:
/tmp/next/build/fs/btrfs/free-space-tree.c: In function 'btrfs_delete_orphan_free_space_entries':
/tmp/next/build/fs/btrfs/free-space-tree.c:1765:9: error: implicit declaration of function 'BTRFS_PATH_AUTO_RELEASE'; did you mean 'BTRFS_PATH_AUTO_FREE'? [-Wimplicit-function-declaration]
1765 | BTRFS_PATH_AUTO_RELEASE(path);
| ^~~~~~~~~~~~~~~~~~~~~~~
| BTRFS_PATH_AUTO_FREE
/tmp/next/build/fs/btrfs/free-space-tree.c:1765:33: error: 'path' undeclared (first use in this function)
1765 | BTRFS_PATH_AUTO_RELEASE(path);
| ^~~~
/tmp/next/build/fs/btrfs/free-space-tree.c:1765:33: note: each undeclared identifier is reported only once for each function it appears in
/tmp/next/build/fs/btrfs/free-space-tree.c:1817:1: error: control reaches end of non-void function [-Werror=return-type]
1817 | }
| ^
cc1: some warnings being treated as errors
Caused by commit
7fcf8455f610b (btrfs: reject new transactions if the fs is fully read-only)
I have used the version from 20260119 instead.
Powered by blists - more mailing lists