From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-unstable 255/261] include/linux/mm.h:1556:29: error: conflicting types for 'page_to_section'; have 'long unsigned int(const struct page *)'
Date: Sat, 18 Jun 2022 22:06:36 +0100 [thread overview]
Message-ID: <Yq4+XF06TsrQ8LmR@casper.infradead.org> (raw)
In-Reply-To: <202206181437.AwvGIkuq-lkp@intel.com>
On Sat, Jun 18, 2022 at 03:00:58PM +0800, kernel test robot wrote:
> config: parisc64-defconfig (https://download.01.org/0day-ci/archive/20220618/202206181437.AwvGIkuq-lkp@intel.com/config)
Ugh, SPARSEMEM without SPARSEMEM_VMEMMAP.
> include/linux/mm.h: In function 'destroy_large_folio':
> >> include/asm-generic/memory_model.h:35:21: error: implicit declaration of function 'page_to_section'; did you mean 'present_section'? [-Werror=implicit-function-declaration]
> include/linux/mm.h:214:38: note: in expansion of macro 'page_to_pfn'
> 214 | #define nth_page(page,n) pfn_to_page(page_to_pfn((page)) + (n))
> | ^~~~~~~~~~~
Needs some rearranging of the header file to make this work.
I don't think it's the right time to do that, and this patch can just be
dropped for this cycle. It shouldn't affect the subsequent patches in
the series, AFAICT.
prev parent reply other threads:[~2022-06-18 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 7:00 [akpm-mm:mm-unstable 255/261] include/linux/mm.h:1556:29: error: conflicting types for 'page_to_section'; have 'long unsigned int(const struct page *)' kernel test robot
2022-06-18 21:06 ` 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=Yq4+XF06TsrQ8LmR@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).