[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180806155440.9dcb271a3b075bd964aec60f@linux-foundation.org>
Date: Mon, 6 Aug 2018 15:54:40 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dan Williams <dan.j.williams@...el.com>,
Michael Ellerman <mpe@...erman.id.au>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: Build regressions/improvements in v4.17-rc1
On Mon, 6 Aug 2018 12:39:21 +0200 Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> CC Dan, Michael, AKPM, powerpc
>
> On Mon, Apr 16, 2018 at 3:10 PM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> > Below is the list of build error/warning regressions/improvements in
> > v4.17-rc1[1] compared to v4.16[2].
>
> I'd like to point your attention to:
>
> > + warning: vmlinux.o(.text+0x376518): Section mismatch in reference from the function .devm_memremap_pages() to the function .meminit.text:.arch_add_memory(): => N/A
> > + warning: vmlinux.o(.text+0x376d64): Section mismatch in reference from the function .devm_memremap_pages_release() to the function .meminit.text:.arch_remove_memory(): => N/A
hm. Dan isn't around at present so we're on our own with this one.
x86 doesn't put arch_add_memory and arch_remove_memory into __meminit.
x86 does
#ifdef CONFIG_MEMORY_HOTPLUG
int arch_add_memory(int nid, u64 start, u64 size, struct vmem_altmap *altmap,
bool want_memblock)
{
...
So I guess powerpc should do that as well?
Powered by blists - more mailing lists