From: Mark Brown <broonie@kernel.org>
To: Jan Kara <jack@suse.cz>, Kyle Zeng <kylebot@openai.com>
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 ext3 tree
Date: Mon, 6 Jul 2026 14:35:27 +0100 [thread overview]
Message-ID: <akuvHyqOUzdSTMnU@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Hi all,
After merging the ext3 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/tmp/next/build/fs/udf/inode.c:2302:37: error: use of undeclared
identifier 'sbi'
2302 | if (eloc->partitionReferenceNum >= sbi->s_partitions) {
| ^
/tmp/next/build/fs/udf/inode.c:2304:35: error: use of undeclared
identifier 'sbi'
2304 | eloc->partitionReferenceNum, sbi->s_partitions);
| ^
Caused by commit
107eb175cbc81 (udf: validate extent partition references in udf_current_aext())
I have used the version from next-20260603 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-07-06 13:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 13:35 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 0:07 linux-next: build failure after merge of the ext3 tree Stephen Rothwell
2024-03-07 6:18 ` Winston Wen
2024-03-07 12:03 ` Jan Kara
2023-08-16 0:37 Stephen Rothwell
2020-11-12 23:47 Stephen Rothwell
2020-11-13 10:33 ` Jan Kara
2019-01-31 4:14 Stephen Rothwell
2019-01-31 10:11 ` Jan Kara
2019-01-31 22:09 ` Stephen Rothwell
2014-08-08 1:52 Stephen Rothwell
2014-08-08 9:22 ` Jan Kara
2011-12-28 0:22 Stephen Rothwell
2012-01-02 22:40 ` Jan Kara
2010-03-02 0:36 Stephen Rothwell
2010-03-02 9:07 ` Christoph Hellwig
2010-03-02 17:27 ` Jan Kara
2010-03-03 0:42 ` 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=akuvHyqOUzdSTMnU@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jack@suse.cz \
--cc=kylebot@openai.com \
--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