From: kernel test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: mm/sparse.c:653:13: sparse: sparse: symbol 'populate_section_memmap' was not declared. Should it be static?
Date: Tue, 5 Jul 2022 21:11:08 +0800 [thread overview]
Message-ID: <202207052117.j1h9ayCI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c1084b6c5620a743f86947caca66d90f24060f56
commit: e9c0a3f05477e18d2dae816cb61b62be1b7e90d3 mm/sparsemem: convert kmalloc_section_memmap() to populate_section_memmap()
date: 3 years ago
config: ia64-randconfig-s031-20220703 (https://download.01.org/0day-ci/archive/20220705/202207052117.j1h9ayCI-lkp@intel.com/config)
compiler: ia64-linux-gcc (GCC) 11.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c0a3f05477e18d2dae816cb61b62be1b7e90d3
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout e9c0a3f05477e18d2dae816cb61b62be1b7e90d3
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=ia64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
mm/sparse.c:213:6: sparse: sparse: symbol 'subsection_mask_set' was not declared. Should it be static?
>> mm/sparse.c:653:13: sparse: sparse: symbol 'populate_section_memmap' was not declared. Should it be static?
vim +/populate_section_memmap +653 mm/sparse.c
638
639 static void depopulate_section_memmap(unsigned long pfn, unsigned long nr_pages,
640 struct vmem_altmap *altmap)
641 {
642 unsigned long start = (unsigned long) pfn_to_page(pfn);
643 unsigned long end = start + nr_pages * sizeof(struct page);
644
645 vmemmap_free(start, end, altmap);
646 }
647 static void free_map_bootmem(struct page *memmap)
648 {
649 unsigned long start = (unsigned long)memmap;
650 unsigned long end = (unsigned long)(memmap + PAGES_PER_SECTION);
651
652 vmemmap_free(start, end, NULL);
> 653 }
654
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-05 13:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202207052117.j1h9ayCI-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.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;
as well as URLs for NNTP newsgroup(s).