From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
David Hildenbrand <david@redhat.com>
Subject: Re: [akpm-mm:mm-unstable 457/479] arch/s390/kernel/uv.c:196:13: error: call to undeclared function 'page_mapping'; ISO C99 and later do not support implicit function declarations
Date: Mon, 29 Apr 2024 09:46:29 -0700 [thread overview]
Message-ID: <20240429094629.77c77ebf0ebb7c4197e8880d@linux-foundation.org> (raw)
In-Reply-To: <Zi0Wye9tY9bofWKh@casper.infradead.org>
On Sat, 27 Apr 2024 16:16:25 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> On Sat, Apr 27, 2024 at 03:54:08PM +0800, kernel test robot wrote:
> > >> arch/s390/kernel/uv.c:196:13: error: call to undeclared function 'page_mapping'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> > 196 | } else if (page_mapping(page)) {
> > | ^
>
> Gah. The removal of page_mapping() is in the s390 tree.
>
> commit 259e660d91d0
> Author: Matthew Wilcox (Oracle) <willy@infradead.org>
> Date: Fri Mar 22 16:11:46 2024 +0000
>
> s390/mm: Convert make_page_secure to use a folio
>
> But we don't want that kind of dependency between the mm and s390 trees,
> so perhaps best to just drop
>
> commit 48f0b417c0fc
> Author: Matthew Wilcox (Oracle) <willy@infradead.org>
> Date: Tue Apr 23 23:55:37 2024 +0100
>
> mm: remove page_mapping()
>
> for now and we can submit it shortly before -rc1?
yep, let's do that.
prev parent reply other threads:[~2024-04-29 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 7:54 [akpm-mm:mm-unstable 457/479] arch/s390/kernel/uv.c:196:13: error: call to undeclared function 'page_mapping'; ISO C99 and later do not support implicit function declarations kernel test robot
2024-04-27 15:16 ` Matthew Wilcox
2024-04-29 16:46 ` Andrew Morton [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=20240429094629.77c77ebf0ebb7c4197e8880d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).