From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the folio tree
Date: Wed, 9 Feb 2022 14:38:04 +1100 [thread overview]
Message-ID: <20220209143804.33b5f08a@canb.auug.org.au> (raw)
In-Reply-To: <20220207150621.0273b095@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
Hi all,
On Mon, 7 Feb 2022 15:06:21 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the folio tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> mm/page_vma_mapped.c: In function 'page_vma_mapped_walk':
> mm/page_vma_mapped.c:219:48: error: implicit declaration of function 'pmd_pfn'; did you mean 'pmd_off'? [-Werror=implicit-function-declaration]
> 219 | if (!check_pmd(pmd_pfn(pmde), pvmw))
> | ^~~~~~~
> | pmd_off
>
> Caused by commit
>
> 02ecfe9b9580 ("mm: Convert page_vma_mapped_walk to work on PFNs")
>
> Presumably you need to explicitly include <linux/pgtable.h>?
>
> I have used the folio tree from next-20220204 for today.
I am still getting this build failure.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-09 4:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 4:06 linux-next: build failure after merge of the folio tree Stephen Rothwell
2022-02-09 3:38 ` Stephen Rothwell [this message]
2022-02-09 3:47 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 8:04 Stephen Rothwell
2022-05-02 10:01 ` Gao Xiang
2022-03-15 10:26 Stephen Rothwell
2022-03-15 14:42 ` Matthew Wilcox
2022-02-28 12:53 Stephen Rothwell
2022-02-17 7:20 Stephen Rothwell
2022-02-15 6:44 Stephen Rothwell
2022-01-04 7:29 Stephen Rothwell
2021-11-01 6:48 Stephen Rothwell
2021-09-21 4:26 Stephen Rothwell
2021-09-22 4:19 ` Stephen Rothwell
2021-11-01 22:05 ` Stephen Rothwell
2021-11-02 7:02 ` David Howells
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=20220209143804.33b5f08a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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