From: Muchun Song <songmuchun@bytedance.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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: Wed, 10 Mar 2021 13:53:30 +0800 [thread overview]
Message-ID: <CAMZfGtURAqAqzWgTmeGcDNeQVhcNLMngPJD2QkwkXqo3R8uF6w@mail.gmail.com> (raw)
In-Reply-To: <20210310145514.3f3743fe@canb.auug.org.au>
On Wed, Mar 10, 2021 at 11:55 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the akpm-current tree, today's linux-next build (sparc64
> defconfig) failed like this:
>
> arch/sparc/mm/init_64.c:2495:4: error: implicit declaration of function 'register_page_bootmem_info_node'; did you mean 'register_page_bootmem_info'? [-Werror=implicit-function-declaration]
> register_page_bootmem_info_node(NODE_DATA(i));
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> register_page_bootmem_info
>
> Caused by commit
>
> cd28b1a6791d ("mm: memory_hotplug: factor out bootmem core functions to bootmem_info.c")
>
> grep is your friend ...
>
> I have applied the following patch for today:
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 10 Mar 2021 14:46:27 +1100
> Subject: [PATCH] fix for "mm: memory_hotplug: factor out bootmem core
> functions to bootmem_info.c"
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Sorry, it is my mistake. Thanks Stephen to fix this. This is the right fix.
> ---
> arch/sparc/mm/init_64.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/sparc/mm/init_64.c b/arch/sparc/mm/init_64.c
> index 182bb7bdaa0a..c709b72e81bf 100644
> --- a/arch/sparc/mm/init_64.c
> +++ b/arch/sparc/mm/init_64.c
> @@ -27,6 +27,7 @@
> #include <linux/percpu.h>
> #include <linux/mmzone.h>
> #include <linux/gfp.h>
> +#include <linux/bootmem_info.h>
>
> #include <asm/head.h>
> #include <asm/page.h>
> --
> 2.30.0
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2021-03-10 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 3:55 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell
2021-03-10 5:53 ` Muchun Song [this message]
2021-05-21 5:53 Stephen Rothwell
2021-05-21 6:09 ` [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=CAMZfGtURAqAqzWgTmeGcDNeQVhcNLMngPJD2QkwkXqo3R8uF6w@mail.gmail.com \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).