lkml.org 
[lkml]   [2020]   [Mar]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: linux-next: build warning after merge of the akpm-current tree
On 03/13/20 at 09:42pm, Stephen Rothwell wrote:
> Hi all,
>
> After merging the akpm-current tree, today's linux-next build (x86_64
> allnoconfig) produced this warning:

I tried with allnoconfig on x86_64, make doesn't trigger below warnings.

Hi Andrew,

Should we fix this kind of warning? If have to, I'll try to make several
macro functions like subsection_map_init does for !CONFIG_SPARSEMEM.

>
> mm/sparse.c:311:12: warning: 'fill_subsection_map' defined but not used [-Wunused-function]
> 311 | static int fill_subsection_map(unsigned long pfn, unsigned long nr_pages)
> | ^~~~~~~~~~~~~~~~~~~
> mm/sparse.c:306:13: warning: 'is_subsection_map_empty' defined but not used [-Wunused-function]
> 306 | static bool is_subsection_map_empty(struct mem_section *ms)
> | ^~~~~~~~~~~~~~~~~~~~~~~
> mm/sparse.c:301:12: warning: 'clear_subsection_map' defined but not used [-Wunused-function]
> 301 | static int clear_subsection_map(unsigned long pfn, unsigned long nr_pages)
> | ^~~~~~~~~~~~~~~~~~~~
>
> Introduced by commits
>
> 38eb09ac7c29 ("mm/sparse.c: introduce new function fill_subsection_map()")
> 334411156ba6 ("mm/sparse.c: introduce a new function clear_subsection_map()")
>
> Or maybe laster patches.
>
> --
> Cheers,
> Stephen Rothwell


\
 
 \ /
  Last update: 2020-03-13 11:56    [W:0.107 / U:10.464 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site