[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202001112247.k6CzgJBj%lkp@intel.com>
Date: Sat, 11 Jan 2020 22:11:25 +0800
From: kbuild test robot <lkp@...el.com>
To: Anshuman Khandual <anshuman.khandual@....com>
Cc: kbuild-all@...ts.01.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
akpm@...ux-foundation.org, catalin.marinas@....com,
will@...nel.org, mark.rutland@....com, david@...hat.com,
cai@....pw, logang@...tatee.com, cpandya@...eaurora.org,
arunks@...eaurora.org, dan.j.williams@...el.com,
mgorman@...hsingularity.net, osalvador@...e.de,
ard.biesheuvel@....com, steve.capper@....com, broonie@...nel.org,
valentin.schneider@....com, Robin.Murphy@....com,
steven.price@....com, suzuki.poulose@....com, ira.weiny@...el.com,
Anshuman Khandual <anshuman.khandual@....com>
Subject: Re: [PATCH V11 1/5] mm/hotplug: Introduce arch callback validating
the hot remove range
Hi Anshuman,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.5-rc5 next-20200110]
[cannot apply to arm64/for-next/core robh/for-next linux/master]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Anshuman-Khandual/arm64-mm-Enable-memory-hot-remove/20200111-003854
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 4a3033ef6e6bb4c566bd1d556de69b494d76976c
config: arm64-randconfig-a001-20200109 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@...el.com>
All errors (new ones prefixed by >>):
mm/memory_hotplug.c: In function 'check_hotremove_memory_range':
>> mm/memory_hotplug.c:1027:7: error: implicit declaration of function 'arch_memory_removable'; did you mean 'add_memory_resource'? [-Werror=implicit-function-declaration]
rc = arch_memory_removable(start, size);
^~~~~~~~~~~~~~~~~~~~~
add_memory_resource
At top level:
mm/memory_hotplug.c:1017:12: warning: 'check_hotremove_memory_range' defined but not used [-Wunused-function]
static int check_hotremove_memory_range(u64 start, u64 size)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +1027 mm/memory_hotplug.c
1016
1017 static int check_hotremove_memory_range(u64 start, u64 size)
1018 {
1019 int rc;
1020
1021 BUG_ON(check_hotplug_memory_range(start, size));
1022
1023 /*
1024 * First check if the platform is willing to have this
1025 * memory range removed else just abort.
1026 */
> 1027 rc = arch_memory_removable(start, size);
1028 if (!rc)
1029 return -EINVAL;
1030
1031 return 0;
1032 }
1033
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
Download attachment ".config.gz" of type "application/gzip" (32289 bytes)
Powered by blists - more mailing lists