From: David Sterba <dsterba@suse.cz>
To: Mark Brown <broonie@kernel.org>
Cc: Boris Burkov <boris@bur.io>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Qu Wenruo <wqu@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the btrfs-fixes tree
Date: Tue, 20 Jan 2026 17:18:38 +0100 [thread overview]
Message-ID: <20260120161838.GD26902@suse.cz> (raw)
In-Reply-To: <aW9wHq0fs8KpLCyj@sirena.org.uk>
On Tue, Jan 20, 2026 at 12:07:58PM +0000, Mark Brown wrote:
> 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.
Sorry, I'll drop the patch from next-fixes.
next prev parent reply other threads:[~2026-01-20 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:07 linux-next: build failure after merge of the btrfs-fixes tree Mark Brown
2026-01-20 12:22 ` Johannes Thumshirn
2026-01-20 12:32 ` Mark Brown
2026-01-20 16:18 ` David Sterba [this message]
2026-01-20 23:33 ` Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2026-01-29 12:51 Mark Brown
2026-02-02 14:57 ` Mark Brown
2026-02-03 7:47 ` David Sterba
2024-03-17 22:17 Stephen Rothwell
2024-03-18 4:50 ` Anand Jain
2024-03-18 17:31 ` David Sterba
2024-03-18 18:58 ` David Sterba
[not found] <20200107082431.2b83a8ac@canb.auug.org.au>
2020-01-07 15:22 ` David Sterba
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=20260120161838.GD26902@suse.cz \
--to=dsterba@suse.cz \
--cc=boris@bur.io \
--cc=broonie@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=wqu@suse.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