From: kbuild test robot <lkp@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: kbuild-all@lists.01.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, akpm@linux-foundation.org,
catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com,
david@redhat.com, cai@lca.pw, logang@deltatee.com,
cpandya@codeaurora.org, arunks@codeaurora.org,
dan.j.williams@intel.com, mgorman@techsingularity.net,
osalvador@suse.de, ard.biesheuvel@arm.com, steve.capper@arm.com,
broonie@kernel.org, valentin.schneider@arm.com,
Robin.Murphy@arm.com, steven.price@arm.com,
suzuki.poulose@arm.com, ira.weiny@intel.com,
Anshuman Khandual <anshuman.khandual@arm.com>
Subject: Re: [PATCH V11 1/5] mm/hotplug: Introduce arch callback validating the hot remove range
Date: Sat, 11 Jan 2020 22:11:25 +0800 [thread overview]
Message-ID: <202001112247.k6CzgJBj%lkp@intel.com> (raw)
In-Reply-To: <1578625755-11792-2-git-send-email-anshuman.khandual@arm.com>
[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]
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@intel.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
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32289 bytes --]
next prev parent reply other threads:[~2020-01-11 14:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 3:09 [PATCH V11 0/5] arm64/mm: Enable memory hot remove Anshuman Khandual
2020-01-10 3:09 ` [PATCH V11 1/5] mm/hotplug: Introduce arch callback validating the hot remove range Anshuman Khandual
2020-01-10 8:42 ` David Hildenbrand
2020-01-13 9:11 ` Anshuman Khandual
2020-01-13 9:14 ` David Hildenbrand
2020-01-13 9:50 ` Anshuman Khandual
2020-01-13 10:37 ` David Hildenbrand
2020-01-14 2:13 ` Anshuman Khandual
2020-01-14 11:09 ` Anshuman Khandual
2020-01-14 12:30 ` David Hildenbrand
2020-01-11 14:11 ` kbuild test robot [this message]
2020-01-13 4:06 ` Anshuman Khandual
2020-01-11 19:49 ` kbuild test robot
2020-01-10 3:09 ` [PATCH V11 2/5] mm/memblock: Introduce MEMBLOCK_BOOT flag Anshuman Khandual
2020-01-13 7:37 ` Mike Rapoport
2020-01-13 8:43 ` Anshuman Khandual
2020-01-13 8:57 ` David Hildenbrand
2020-01-10 3:09 ` [PATCH V11 3/5] of/fdt: Mark boot memory with MEMBLOCK_BOOT Anshuman Khandual
2020-01-10 3:09 ` [PATCH V11 4/5] arm64/mm: Hold memory hotplug lock while walking for kernel page table dump Anshuman Khandual
2020-01-10 3:09 ` [PATCH V11 5/5] arm64/mm: Enable memory hot remove Anshuman Khandual
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=202001112247.k6CzgJBj%lkp@intel.com \
--to=lkp@intel.com \
--cc=Robin.Murphy@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ard.biesheuvel@arm.com \
--cc=arunks@codeaurora.org \
--cc=broonie@kernel.org \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=cpandya@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=ira.weiny@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=mark.rutland@arm.com \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=steve.capper@arm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=valentin.schneider@arm.com \
--cc=will@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