All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [intel-linux-intel-lts:4.19/android_r 20730/22631] arch/parisc/mm/init.c:734:2: error: implicit declaration of function 'memblocks_present'; did you mean 'memblock_reserve'?
Date: Sat, 10 Apr 2021 03:23:15 +0800	[thread overview]
Message-ID: <202104100310.vXPC8mGF-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2447 bytes --]

Hi Helge,

FYI, the error/warning still remains.

tree:   https://github.com/intel/linux-intel-lts.git 4.19/android_r
head:   072f407465e8e25a3c2c22590e1ab72ccf335151
commit: 36960edcc32ce26bcf470e6129c4dc26a44e97ca [20730/22631] UPSTREAM: parisc: Switch from DISCONTIGMEM to SPARSEMEM
config: parisc-randconfig-r035-20210409 (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/intel/linux-intel-lts/commit/36960edcc32ce26bcf470e6129c4dc26a44e97ca
        git remote add intel-linux-intel-lts https://github.com/intel/linux-intel-lts.git
        git fetch --no-tags intel-linux-intel-lts 4.19/android_r
        git checkout 36960edcc32ce26bcf470e6129c4dc26a44e97ca
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/parisc/mm/init.c: In function 'pagetable_init':
   arch/parisc/mm/init.c:655:17: warning: variable 'end_paddr' set but not used [-Wunused-but-set-variable]
     655 |   unsigned long end_paddr;
         |                 ^~~~~~~~~
   arch/parisc/mm/init.c: In function 'paging_init':
>> arch/parisc/mm/init.c:734:2: error: implicit declaration of function 'memblocks_present'; did you mean 'memblock_reserve'? [-Werror=implicit-function-declaration]
     734 |  memblocks_present();
         |  ^~~~~~~~~~~~~~~~~
         |  memblock_reserve
   cc1: some warnings being treated as errors


vim +734 arch/parisc/mm/init.c

   721	
   722	void __init paging_init(void)
   723	{
   724		setup_bootmem();
   725		pagetable_init();
   726		gateway_init();
   727		flush_cache_all_local(); /* start with known state */
   728		flush_tlb_all_local(NULL);
   729	
   730		/*
   731		 * Mark all memblocks as present for sparsemem using
   732		 * memory_present() and then initialize sparsemem.
   733		 */
 > 734		memblocks_present();
   735		sparse_init();
   736		parisc_bootmem_free();
   737	}
   738	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 21528 bytes --]

             reply	other threads:[~2021-04-09 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 19:23 kernel test robot [this message]
2021-04-09 20:23 ` [intel-linux-intel-lts:4.19/android_r 20730/22631] arch/parisc/mm/init.c:734:2: error: implicit declaration of function 'memblocks_present'; did you mean 'memblock_reserve'? Helge Deller
2021-04-10  7:26   ` Greg Kroah-Hartman
2021-04-10  9:11     ` Helge Deller
2021-04-13  1:43     ` Rong Chen
  -- strict thread matches above, loose matches on Subject: below --
2021-04-09 17:55 kernel test robot

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=202104100310.vXPC8mGF-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.