From: Muchun Song <songmuchun@bytedance•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation•org>,
Mike Kravetz <mike.kravetz@oracle•com>,
Oscar Salvador <osalvador@suse•de>,
Michal Hocko <mhocko@suse•com>,
David Hildenbrand <david@redhat•com>,
Matthew Wilcox <willy@infradead•org>,
Xiongchun Duan <duanxiongchun@bytedance•com>,
Anshuman Khandual <anshuman.khandual@arm•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: [External] linux-next: build failure after merge of the akpm-current tree
Date: Fri, 21 May 2021 14:09:56 +0800 [thread overview]
Message-ID: <CAMZfGtXSvWVbLwp-0SjoVub5z94nQyu1tL2jHffQCn32Ebaf7w@mail.gmail.com> (raw)
In-Reply-To: <20210521155359.13b023ff@canb.auug.org.au>
On Fri, May 21, 2021 at 1:54 PM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> After merging the akpm-current tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> mm/migrate.c: In function 'unmap_and_move_huge_page':
> mm/migrate.c:1295:6: error: implicit declaration of function 'hugetlb_page_subpool' [-Werror=implicit-function-declaration]
> 1295 | if (hugetlb_page_subpool(hpage) && !page_mapping(hpage)) {
> | ^~~~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
> b63794a67ae2 ("mm: migrate: fix missing update page_private to hugetlb_page_subpool")
>
> CONFIG_HUGETLB_PAGE is not defined for this build.
>
> I have reverted that commit for today.
Thanks for your test. It has been fixed by the following patch.
https://lore.kernel.org/linux-mm/20210521022747.35736-1-songmuchun@bytedance.com/
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2021-05-21 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 5:53 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell
2021-05-21 6:09 ` Muchun Song [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-10 3:55 Stephen Rothwell
2021-03-10 5:53 ` [External] " Muchun Song
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=CAMZfGtXSvWVbLwp-0SjoVub5z94nQyu1tL2jHffQCn32Ebaf7w@mail.gmail.com \
--to=songmuchun@bytedance$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=anshuman.khandual@arm$(echo .)com \
--cc=david@redhat$(echo .)com \
--cc=duanxiongchun@bytedance$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhocko@suse$(echo .)com \
--cc=mike.kravetz@oracle$(echo .)com \
--cc=osalvador@suse$(echo .)de \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=willy@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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