From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>,
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 mm-hotfixes tree
Date: Tue, 13 Dec 2022 09:30:54 +1100 [thread overview]
Message-ID: <20221213093054.5211da74@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Hi all,
After merging the mm-hotfixes tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/ksm.c: In function 'ksm_might_need_to_copy':
mm/ksm.c:2605:21: error: implicit declaration of function 'copy_mc_user_highpage'; did you mean 'copy_user_highpage'? [-Werror=implicit-function-declaration]
2605 | if (copy_mc_user_highpage(new_page, page, address, vma)) {
| ^~~~~~~~~~~~~~~~~~~~~
| copy_user_highpage
Caused by commit
b7edf4b1cdb1 ("mm: hwpoison: support recovery from ksm_might_need_to_copy()")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-12-12 22:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 22:30 Stephen Rothwell [this message]
2022-12-13 1:34 ` linux-next: build failure after merge of the mm-hotfixes tree Kefeng Wang
2022-12-13 2:23 ` Andrew Morton
2022-12-13 2:45 ` Stephen Rothwell
2022-12-13 2:54 ` Kefeng Wang
-- strict thread matches above, loose matches on Subject: below --
2023-12-13 22:18 Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett
2022-11-25 1:10 Stephen Rothwell
2022-11-25 5:24 ` Juergen Gross
2022-11-25 5:24 ` Andrew Morton
2022-11-25 5:48 ` Stephen Rothwell
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=20221213093054.5211da74@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=wangkefeng.wang@huawei.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).