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: linux-next: build failure after merge of the folio tree
Date: Thu, 17 Feb 2022 18:20:13 +1100 [thread overview]
Message-ID: <20220217182013.45aa8e3f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
Hi all,
After merging the folio tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/mmap.c: In function 'do_mas_align_munmap':
mm/mmap.c:2373:25: error: implicit declaration of function 'munlock_vma_pages_all'; did you mean 'munlock_vma_page'? [-Werror=implicit-function-declaration]
2373 | munlock_vma_pages_all(next);
| ^~~~~~~~~~~~~~~~~~~~~
| munlock_vma_page
mm/mmap.c: In function 'do_brk_munmap':
mm/mmap.c:2906:17: error: implicit declaration of function 'munlock_vma_pages_range'; did you mean 'count_vma_pages_range'? [-Werror=implicit-function-declaration]
2906 | munlock_vma_pages_range(&unmap, newbrk, oldbrk);
| ^~~~~~~~~~~~~~~~~~~~~~~
| count_vma_pages_range
This is undoubtably due to something I missed in the merge resolution,
so I am giving up on merging the folio tree again today and am back to
the version from next-20220204 again.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-02-17 7:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 7:20 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 8:04 linux-next: build failure after merge of the folio tree 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-15 6:44 Stephen Rothwell
2022-02-07 4:06 Stephen Rothwell
2022-02-09 3:38 ` Stephen Rothwell
2022-02-09 3:47 ` Matthew Wilcox
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=20220217182013.45aa8e3f@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