From: Mark Brown <broonie@kernel.org>
To: Jeff Layton <jlayton@kernel.org>,
Ilya Dryomov <idryomov@gmail.com>, Chao Yu <chao@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 ceph tree
Date: Thu, 27 Aug 2026 14:09:51 +0100 [thread overview]
Message-ID: <apA3H9wjxmEywmk5@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
Hi all,
After merging the ceph tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/tmp/next/build/fs/ceph/addr.c:947:4: error: call to undeclared function 'fscrypt_finalize_bounce_page'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
947 | fscrypt_finalize_bounce_page(&osd_data->pages[j]);
| ^
/tmp/next/build/fs/ceph/addr.c:947:4: note: did you mean 'fscrypt_free_bounce_page'?
/tmp/next/build/include/linux/fscrypt.h:380:6: note: 'fscrypt_free_bounce_page' declared here
380 | void fscrypt_free_bounce_page(struct page *bounce_page);
| ^
Caused by commit
0137f53184252 (ceph: use fscrypt_finalize_bounce_page() for cleanup)
I have used the tree from next-20260826 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-08-27 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 13:09 Mark Brown [this message]
2026-08-27 14:54 ` Ilya Dryomov
-- strict thread matches above, loose matches on Subject: below --
2020-12-14 23:46 Stephen Rothwell
2013-09-27 1:31 Stephen Rothwell
2013-09-27 2:36 ` Dave Kleikamp
2013-09-26 1:15 Stephen Rothwell
2013-09-26 1:20 ` majianpeng
2013-09-26 1:26 ` Sage Weil
2012-03-21 1:40 Stephen Rothwell
2012-03-21 4:24 ` Alex Elder
2010-11-16 23:43 Stephen Rothwell
2010-11-17 0:02 ` Sage Weil
2010-09-20 1:41 Stephen Rothwell
2010-09-20 2:53 ` Sage Weil
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=apA3H9wjxmEywmk5@sirena.org.uk \
--to=broonie@kernel.org \
--cc=chao@kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--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
all inboxes | Powered by JetHome®