From: Andrew Morton <akpm@linux-foundation.org>
To: Tony Luck <tony.luck@gmail.com>
Cc: Mathieu Malaterre <malat@debian.org>,
linux-mm@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/memblock: add missing include <linux/bootmem.h>
Date: Fri, 15 Jun 2018 12:17:16 -0700 [thread overview]
Message-ID: <20180615121716.37fb93385825b0b2f59240cc@linux-foundation.org> (raw)
In-Reply-To: <CA+8MBbKj4A5kh=hE0vcadzD+=cEAFY7OCWFCzvubu6cWULCJ0A@mail.gmail.com>
On Fri, 15 Jun 2018 11:59:10 -0700 Tony Luck <tony.luck@gmail.com> wrote:
> On Wed, Jun 6, 2018 at 12:41 PM, Mathieu Malaterre <malat@debian.org> wrote:
> > Commit 26f09e9b3a06 ("mm/memblock: add memblock memory allocation apis")
> > introduced two new function definitions:
> > a??memblock_virt_alloc_try_nid_nopanica??
> > and
> > a??memblock_virt_alloc_try_nida??.
> > Commit ea1f5f3712af ("mm: define memblock_virt_alloc_try_nid_raw")
> > introduced the following function definition:
> > a??memblock_virt_alloc_try_nid_rawa??
> >
> > This commit adds an includeof header file <linux/bootmem.h> to provide the
> > missing function prototypes. Silence the following gcc warning (W=1):
> >
> > mm/memblock.c:1334:15: warning: no previous prototype for a??memblock_virt_alloc_try_nid_rawa?? [-Wmissing-prototypes]
> > mm/memblock.c:1371:15: warning: no previous prototype for a??memblock_virt_alloc_try_nid_nopanica?? [-Wmissing-prototypes]
> > mm/memblock.c:1407:15: warning: no previous prototype for a??memblock_virt_alloc_try_nida?? [-Wmissing-prototypes]
> >
> > Signed-off-by: Mathieu Malaterre <malat@debian.org>
>
> Sadly that breaks ia64 build:
>
> CC mm/memblock.o
> mm/memblock.c:1340: error: redefinition of a??memblock_virt_alloc_try_nid_rawa??
> ./include/linux/bootmem.h:335: error: previous definition of
> a??memblock_virt_alloc_try_nid_rawa?? was here
> mm/memblock.c:1377: error: redefinition of a??memblock_virt_alloc_try_nid_nopanica??
> ./include/linux/bootmem.h:343: error: previous definition of
> a??memblock_virt_alloc_try_nid_nopanica?? was here
> mm/memblock.c:1413: error: redefinition of a??memblock_virt_alloc_try_nida??
> ./include/linux/bootmem.h:327: error: previous definition of
> a??memblock_virt_alloc_try_nida?? was here
> make[1]: *** [mm/memblock.o] Error 1
> make: *** [mm/memblock.o] Error 2
Huh. How did that ever work. I guess it's either this:
--- a/mm/Makefile~a
+++ a/mm/Makefile
@@ -45,6 +45,7 @@ obj-y += init-mm.o
ifdef CONFIG_NO_BOOTMEM
obj-y += nobootmem.o
+ obj-$(CONFIG_HAVE_MEMBLOCK) += memblock.o
else
obj-y += bootmem.o
endif
@@ -53,7 +54,6 @@ obj-$(CONFIG_ADVISE_SYSCALLS) += fadvise
ifdef CONFIG_MMU
obj-$(CONFIG_ADVISE_SYSCALLS) += madvise.o
endif
-obj-$(CONFIG_HAVE_MEMBLOCK) += memblock.o
obj-$(CONFIG_SWAP) += page_io.o swap_state.o swapfile.o swap_slots.o
obj-$(CONFIG_FRONTSWAP) += frontswap.o
or this:
--- a/include/linux/bootmem.h~a
+++ a/include/linux/bootmem.h
@@ -154,7 +154,7 @@ extern void *__alloc_bootmem_low_node(pg
__alloc_bootmem_low_node(pgdat, x, PAGE_SIZE, 0)
-#if defined(CONFIG_HAVE_MEMBLOCK) && defined(CONFIG_NO_BOOTMEM)
+#if defined(CONFIG_HAVE_MEMBLOCK)
/* FIXME: use MEMBLOCK_ALLOC_* variants here */
#define BOOTMEM_ALLOC_ACCESSIBLE 0
and I'm not sure which. I think I'll just revert $subject for now.
next prev parent reply other threads:[~2018-06-15 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 19:41 Mathieu Malaterre
2018-06-15 18:59 ` Tony Luck
2018-06-15 19:17 ` Andrew Morton [this message]
2018-06-15 22:26 ` Tony Luck
2018-06-15 23:32 ` Luck, Tony
2018-06-21 18:06 ` Paul Burton
2018-06-21 23:34 ` 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=20180615121716.37fb93385825b0b2f59240cc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=malat@debian.org \
--cc=tony.luck@gmail.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