From: kbuild test robot <fengguang.wu@intel.com>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: kbuild-all@01.org, "Matwey V. Kornilov" <matwey@sai.msu.ru>,
Wen Congyang <wency@cn.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [matwey:bbb-3.8-v4 977/1465] drivers//acpi/acpi_memhotplug.c:302:12: error: too many arguments to function 'remove_memory'
Date: Sun, 11 Feb 2018 20:33:32 +0800 [thread overview]
Message-ID: <201802112029.HiNJujj8%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2318 bytes --]
tree: https://github.com/matwey/linux bbb-3.8-v4
head: 95ce62d197bf09acc7489ecdb72c1c1f03ad7ba5
commit: b3562b3bc64b081f51a74c391aaf5be78c7066c0 [977/1465] memory-hotplug: remove sysfs file of node
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout b3562b3bc64b081f51a74c391aaf5be78c7066c0
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers//acpi/acpi_memhotplug.c: In function 'acpi_memory_remove_memory':
>> drivers//acpi/acpi_memhotplug.c:302:12: error: too many arguments to function 'remove_memory'
result = remove_memory(nid, info->start_addr, info->length);
^~~~~~~~~~~~~
In file included from include/linux/mmzone.h:761:0,
from include/linux/gfp.h:4,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from drivers//acpi/acpi_memhotplug.c:29:
include/linux/memory_hotplug.h:250:12: note: declared here
extern int remove_memory(u64 start, u64 size);
^~~~~~~~~~~~~
vim +/remove_memory +302 drivers//acpi/acpi_memhotplug.c
280
281 static int acpi_memory_remove_memory(struct acpi_memory_device *mem_device)
282 {
283 int result = 0, nid;
284 struct acpi_memory_info *info, *n;
285
286 nid = acpi_get_node(mem_device->device->handle);
287
288 list_for_each_entry_safe(info, n, &mem_device->res_list, list) {
289 if (info->failed)
290 /* The kernel does not use this memory block */
291 continue;
292
293 if (!info->enabled)
294 /*
295 * The kernel uses this memory block, but it may be not
296 * managed by us.
297 */
298 return -EBUSY;
299
300 if (nid < 0)
301 nid = memory_add_physaddr_to_nid(info->start_addr);
> 302 result = remove_memory(nid, info->start_addr, info->length);
303 if (result)
304 return result;
305
306 list_del(&info->list);
307 kfree(info);
308 }
309
310 return result;
311 }
312
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31335 bytes --]
reply other threads:[~2018-02-11 12:34 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=201802112029.HiNJujj8%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=matwey@sai.msu.ru \
--cc=tangchen@cn.fujitsu.com \
--cc=wency@cn.fujitsu.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