From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-stable 290/329] lib/iov_iter.c:474:7: error: call to undeclared function 'folio_test_partial_kmap'; ISO C99 and later do not support implicit function declarations
Date: Mon, 2 Jun 2025 16:00:11 +0100 [thread overview]
Message-ID: <aD28e-twOPaE1Yin@casper.infradead.org> (raw)
In-Reply-To: <202506022027.IYQzZghL-lkp@intel.com>
On Mon, Jun 02, 2025 at 08:12:44PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-stable
> head: 0b43b8bc8ef88bb45b018b2d4853d38bfc5ce2a7
> commit: d9736929445e7f4c60f0093af61ff0b52e2d4412 [290/329] iov: remove copy_page_from_iter_atomic()
Thanks!
> >> lib/iov_iter.c:474:7: error: call to undeclared function 'folio_test_partial_kmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 474 | if (folio_test_partial_kmap(folio) &&
It looks like mm-stable is based on the wrong commit. It appears to
be based on v6.15-rc6 while folio_test_partial_kmap() was added during
the v6.16 merge window. While Linus' tree will never fail to build,
anyone ending up on this branch due to a bisect decision will find an
unbuildable tree.
prev parent reply other threads:[~2025-06-02 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 12:12 [akpm-mm:mm-stable 290/329] lib/iov_iter.c:474:7: error: call to undeclared function 'folio_test_partial_kmap'; ISO C99 and later do not support implicit function declarations kernel test robot
2025-06-02 15:00 ` Matthew Wilcox [this message]
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=aD28e-twOPaE1Yin@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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