From: Luiz Capitulino <luizcap@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 5933/6583] include/linux/page_ext.h:131:20: error: call to undeclared function 'page_to_section'; ISO C99 and later do not support implicit function declarations
Date: Wed, 26 Feb 2025 09:24:11 -0500 [thread overview]
Message-ID: <8cece92a-6ad0-43fe-9916-eeb850c039e1@redhat.com> (raw)
In-Reply-To: <e5aec89c-a7d5-453a-8883-e3c025db2e5b@app.fastmail.com>
On 2025-02-26 09:10, Arnd Bergmann wrote:
> On Wed, Feb 26, 2025, at 10:46, kernel test robot wrote:
>> commit: a2d6e9c1a867bb9f13943cb8483e2ab85b630bcd [5933/6583] mm:
>> page_ext: add an iteration API for page extensions
>> config: i386-buildonly-randconfig-004-20250226
>
>>
>> In file included from arch/x86/kernel/asm-offsets.c:14:
>> In file included from include/linux/suspend.h:5:
>> In file included from include/linux/swap.h:9:
>> In file included from include/linux/memcontrol.h:21:
>> In file included from include/linux/mm.h:8:
>> In file included from include/linux/pgalloc_tag.h:12:
>>>> include/linux/page_ext.h:131:20: error: call to undeclared function 'page_to_section'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>> 131 | iter->start_pfn = page_to_pfn(page);
>> | ^
>> include/asm-generic/memory_model.h:64:21: note: expanded from macro
>> 'page_to_pfn'
>> 64 | #define page_to_pfn __page_to_pfn
>
> I'm getting this on all configurations that set CONFIG_SPARSEMEM
> but not CONFIG_SPARSEMEM_VMMEMMAP.
Oh, thanks. I didn't build with CONFIG_SPARSEMEM_VMEMMAP=n.
> There is also a possible problem with linux/page_ext.h
> including pgtable.h and mmzone.h, which I think can lead
> to circular header inclusions with linux/mm.h.
Thanks, I'll look into this.
Andrew, I think you'll have to drop this for now. I may not
have the time to look into this this week.
next prev parent reply other threads:[~2025-02-26 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 9:46 kernel test robot
2025-02-26 14:10 ` Arnd Bergmann
2025-02-26 14:24 ` Luiz Capitulino [this message]
2025-02-26 20:31 ` Andrew Morton
2025-02-28 13:17 ` David Hildenbrand
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=8cece92a-6ad0-43fe-9916-eeb850c039e1@redhat.com \
--to=luizcap@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--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