From: Mark Brown <broonie@kernel•org>
To: David Sterba <dsterba@suse•cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the btrfs-fixes tree
Date: Thu, 29 Jan 2026 12:51:15 +0000 [thread overview]
Message-ID: <aXtXw3_wMDnrrOxW@sirena.org.uk> (raw)
Hi all,
After merging the btrfs-fixes tree, today's linux-next build
(arm64 defconfig) failed like this:
/tmp/next/build/fs/btrfs/bio.c: In function 'btrfs_split_bio':
/tmp/next/build/fs/btrfs/bio.c:102:13: error: 'struct btrfs_bio' has no member named 'can_use_append'
102 | bbio->can_use_append = orig_bbio->can_use_append;
| ^~
/tmp/next/build/fs/btrfs/bio.c:102:41: error: 'struct btrfs_bio' has no member named 'can_use_append'
102 | bbio->can_use_append = orig_bbio->can_use_append;
| ^~
/tmp/next/build/fs/btrfs/bio.c:104:13: error: 'struct btrfs_bio' has no member named 'is_remap'
104 | bbio->is_remap = orig_bbio->is_remap;
| ^~
/tmp/next/build/fs/btrfs/bio.c:104:35: error: 'struct btrfs_bio' has no member named 'is_remap'
104 | bbio->is_remap = orig_bbio->is_remap;
| ^~
Caused by commit
4b40b1c47f937 (btrfs: fix copying the flags of btrfs_bio after split)
I have used the version from 20260128 instead.
next reply other threads:[~2026-01-29 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 12:51 Mark Brown [this message]
2026-02-02 14:57 ` linux-next: build failure after merge of the btrfs-fixes tree Mark Brown
2026-02-03 7:47 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2026-01-20 12:07 Mark Brown
2026-01-20 12:22 ` Johannes Thumshirn
2026-01-20 12:32 ` Mark Brown
2026-01-20 16:18 ` David Sterba
2026-01-20 23:33 ` Qu Wenruo
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=aXtXw3_wMDnrrOxW@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=dsterba@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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