From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kent Overstreet <kent.overstreet@linux.dev>
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 bcachefs tree
Date: Mon, 13 Nov 2023 09:30:46 +1100 [thread overview]
Message-ID: <20231113093046.7b79407e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
Hi all,
After merging the bcachefs tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/bcachefs/inode.c: In function 'may_delete_deleted_inode':
fs/bcachefs/inode.c:1129:43: error: 'BTREE_INSERT_NOFAIL' undeclared (first use in this function)
1129 | BTREE_INSERT_NOFAIL|
| ^~~~~~~~~~~~~~~~~~~
fs/bcachefs/inode.c:1129:43: note: each undeclared identifier is reported only once for each function it appears in
fs/bcachefs/inode.c:1130:43: error: 'BTREE_INSERT_LAZY_RW' undeclared (first use in this function)
1130 | BTREE_INSERT_LAZY_RW);
| ^~~~~~~~~~~~~~~~~~~~
Caused by commit
4b8cc695db52 ("bcachefs: Rename BTREE_INSERT flags")
interacting with commit
897d32dffe59 ("bcachefs: Fix missing transaction commit")
I have used the bcachefs tree from next-20231110 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-11-12 22:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 22:30 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-11 23:54 linux-next: build failure after merge of the bcachefs tree Stephen Rothwell
2024-02-14 0:16 ` Kees Cook
2024-02-14 0:29 ` Kent Overstreet
2024-02-14 0:39 ` Darrick J. Wong
2024-02-14 1:09 ` Kees Cook
2024-02-07 0:57 Stephen Rothwell
2024-02-08 22:46 ` Stephen Rothwell
2024-02-08 23:59 ` Kent Overstreet
2023-11-15 23:02 Stephen Rothwell
2023-09-12 2:04 Stephen Rothwell
2023-09-12 2:47 ` Qi Zheng
2023-09-12 23:35 ` Stephen Rothwell
2023-09-13 1:10 ` Qi Zheng
2023-09-13 20:23 ` Andrew Morton
2023-09-13 22:31 ` Stephen Rothwell
2023-11-01 0:32 ` Stephen Rothwell
2023-11-01 0:53 ` Kent Overstreet
2023-11-01 1:14 ` Stephen Rothwell
2023-09-13 22:14 ` Stephen Rothwell
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=20231113093046.7b79407e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).