linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: kbuild-all@01.org, "Matwey V. Kornilov" <matwey@sai.msu.ru>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [matwey:bbb-3.8-3.9 160/312] drivers/acpi/processor_driver.c:645:2: error: implicit declaration of function 'try_offline_node'
Date: Sat, 3 Feb 2018 03:32:47 +0800	[thread overview]
Message-ID: <201802030333.T7bBsjwY%fengguang.wu@intel.com> (raw)

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

tree:   https://github.com/matwey/linux bbb-3.8-3.9
head:   f24c5d4dc718b210b6a2d874187f43e63b99d162
commit: 05c2105e30f5c2d8cb486ff5fd20059b401ddbb9 [160/312] cpu-hotplug, memory-hotplug: try offlining the node when hotremoving a cpu
config: i386-randconfig-a1-201804 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        git checkout 05c2105e30f5c2d8cb486ff5fd20059b401ddbb9
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/acpi/processor_driver.c: In function 'acpi_processor_remove':
>> drivers/acpi/processor_driver.c:645:2: error: implicit declaration of function 'try_offline_node' [-Werror=implicit-function-declaration]
     try_offline_node(cpu_to_node(pr->id));
     ^
   cc1: some warnings being treated as errors

vim +/try_offline_node +645 drivers/acpi/processor_driver.c

   613	
   614	static int acpi_processor_remove(struct acpi_device *device)
   615	{
   616		struct acpi_processor *pr = NULL;
   617	
   618	
   619		if (!device || !acpi_driver_data(device))
   620			return -EINVAL;
   621	
   622		pr = acpi_driver_data(device);
   623	
   624		if (pr->id >= nr_cpu_ids)
   625			goto free;
   626	
   627		if (device->removal_type == ACPI_BUS_REMOVAL_EJECT) {
   628			if (acpi_processor_handle_eject(pr))
   629				return -EINVAL;
   630		}
   631	
   632		acpi_processor_power_exit(pr);
   633	
   634		sysfs_remove_link(&device->dev.kobj, "sysdev");
   635	
   636		if (pr->cdev) {
   637			sysfs_remove_link(&device->dev.kobj, "thermal_cooling");
   638			sysfs_remove_link(&pr->cdev->device.kobj, "device");
   639			thermal_cooling_device_unregister(pr->cdev);
   640			pr->cdev = NULL;
   641		}
   642	
   643		per_cpu(processors, pr->id) = NULL;
   644		per_cpu(processor_device_array, pr->id) = NULL;
 > 645		try_offline_node(cpu_to_node(pr->id));
   646	
   647	free:
   648		free_cpumask_var(pr->throttling.shared_cpu_map);
   649		kfree(pr);
   650	
   651		return 0;
   652	}
   653	

---
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: 19502 bytes --]

                 reply	other threads:[~2018-02-02 19:33 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=201802030333.T7bBsjwY%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