From: Baoquan He <bhe@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, rppt@kernel.org
Subject: Re: [PATCH] mm: fix prototype warning from kernel test robot
Date: Fri, 22 Jan 2021 16:46:59 +0800 [thread overview]
Message-ID: <20210122084659.GA29905@MiWiFi-R3L-srv> (raw)
In-Reply-To: <3fd62f11-bf44-3ede-aed1-10d9d4849f00@redhat.com>
On 01/22/21 at 09:40am, David Hildenbrand wrote:
> On 22.01.21 08:03, Baoquan He wrote:
> > Kernel test robot calling make with 'W=1' triggering warning like below
> > below for memmap_init_zone() function.
> >
> > mm/page_alloc.c:6259:23: warning: no previous prototype for 'memmap_init_zone' [-Wmissing-prototypes]
> > 6259 | void __meminit __weak memmap_init_zone(unsigned long size, int nid,
> > | ^~~~~~~~~~~~~~~~
> >
> > Fix it by adding the function declaration in include/linux/mm.h.
> > Since memmap_init_zone() has a generic version with '__weak',
> > the declaratoin in ia64 header file can be simply removed.
> >
> > Signed-off-by: Baoquan He <bhe@redhat.com>
> > Reported-by: kernel test robot <lkp@intel.com>
> > ---
> > arch/ia64/include/asm/pgtable.h | 5 -----
> > include/linux/mm.h | 1 +
> > 2 files changed, 1 insertion(+), 5 deletions(-)
> >
> > diff --git a/arch/ia64/include/asm/pgtable.h b/arch/ia64/include/asm/pgtable.h
> > index 2c81394a2430..9b4efe89e62d 100644
> > --- a/arch/ia64/include/asm/pgtable.h
> > +++ b/arch/ia64/include/asm/pgtable.h
> > @@ -517,11 +517,6 @@ extern struct page *zero_page_memmap_ptr;
> > __changed; \
> > })
> > #endif
> > -
> > -# ifdef CONFIG_VIRTUAL_MEM_MAP
> > - /* arch mem_map init routine is needed due to holes in a virtual mem_map */
> > - extern void memmap_init_zone(struct zone *zone);
> > -# endif /* CONFIG_VIRTUAL_MEM_MAP */
> > # endif /* !__ASSEMBLY__ */
> >
> > /*
> > diff --git a/include/linux/mm.h b/include/linux/mm.h
> > index 56bb239f9150..073049bd0b29 100644
> > --- a/include/linux/mm.h
> > +++ b/include/linux/mm.h
> > @@ -2401,6 +2401,7 @@ extern void set_dma_reserve(unsigned long new_dma_reserve);
> > extern void memmap_init_range(unsigned long, int, unsigned long,
> > unsigned long, unsigned long, enum meminit_context,
> > struct vmem_altmap *, int migratetype);
> > +extern void memmap_init_zone(struct zone *zone);
> > extern void setup_per_zone_wmarks(void);
> > extern int __meminit init_per_zone_wmark_min(void);
> > extern void mem_init(void);
> >
>
> This patch is on top of your other series, no?
>
> In -next, we have
>
> extern void memmap_init_zone(unsigned long, int, unsigned long, ...
>
> In that file, so something is wrong.
Right, this one is based on the memmap_init_xx clean up patchset. I
mentioned this the the sub-thread of kernel test robot reporting issues.
next prev parent reply other threads:[~2021-01-22 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 7:03 Baoquan He
2021-01-22 8:40 ` David Hildenbrand
2021-01-22 8:46 ` Baoquan He [this message]
2021-01-22 8:55 ` David Hildenbrand
2021-01-22 8:58 ` Baoquan He
2021-01-22 9:08 ` David Hildenbrand
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=20210122084659.GA29905@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
/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