From: Mark Brown <broonie@kernel•org>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software•com>,
Joanne Koong <joannelkoong@gmail•com>,
Christian Brauner <brauner@kernel•org>
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 ntfs3 tree
Date: Mon, 26 Jan 2026 13:07:54 +0000 [thread overview]
Message-ID: <aXdnKldyCVLxrk78@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Hi all,
After merging the ntfs3 tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
/tmp/next/build/fs/ntfs3/inode.c: In function 'ntfs_read_folio':
/tmp/next/build/fs/ntfs3/inode.c:678:9: error: too few arguments to function 'iomap_read_folio'
678 | iomap_read_folio(&ntfs_iomap_ops, &ctx);
| ^~~~~~~~~~~~~~~~
In file included from /tmp/next/build/fs/ntfs3/inode.c:15:
/tmp/next/build/include/linux/iomap.h:347:6: note: declared here
347 | void iomap_read_folio(const struct iomap_ops *ops,
| ^~~~~~~~~~~~~~~~
/tmp/next/build/fs/ntfs3/inode.c: In function 'ntfs_readahead':
/tmp/next/build/fs/ntfs3/inode.c:702:9: error: too few arguments to function 'iomap_readahead'
702 | iomap_readahead(&ntfs_iomap_ops, &ctx);
| ^~~~~~~~~~~~~~~
/tmp/next/build/include/linux/iomap.h:349:6: note: declared here
349 | void iomap_readahead(const struct iomap_ops *ops,
| ^~~~~~~~~~~~~~~
Caused by commit
099ef9ab9203d (fs/ntfs3: implement iomap-based file operations)
interacting with commit
b2f35ac4146d3 (iomap: add caller-provided callbacks for read and readahead)
from Linus' tree. I have moved the merge fixup from the vfs-brauner
tree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-01-26 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 13:07 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-05 22:57 linux-next: build failure after merge of the ntfs3 tree Stephen Rothwell
2025-11-10 9:47 ` Konstantin Komarov
2022-11-14 23:17 Stephen Rothwell
2022-11-17 8:56 ` Christian Brauner
2022-11-17 10:04 ` 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=aXdnKldyCVLxrk78@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=almaz.alexandrovich@paragon-software$(echo .)com \
--cc=brauner@kernel$(echo .)org \
--cc=joannelkoong@gmail$(echo .)com \
--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