[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201509300812.KVdM5pN3%fengguang.wu@intel.com>
Date: Wed, 30 Sep 2015 08:36:00 +0800
From: kbuild test robot <lkp@...el.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: kbuild-all@...org, Linux PM list <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Alan Stern <stern@...land.harvard.edu>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Daniel Vetter <daniel.vetter@...el.com>
Subject: Re: [RFC][PATCH 2/2] PM / sleep: Kick devices that might have been
reset by firmware
Hi Rafael,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
config: i386-randconfig-a0-201539 (attached as .config)
reproduce:
git checkout 270cc782e8ef117ccad348c9a8330501dcb55f95
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings (new ones prefixed by >>):
drivers/base/power/main.c: In function 'device_complete':
>> drivers/base/power/main.c:936:36: error: implicit declaration of function 'pm_resume_via_firmware' [-Werror=implicit-function-declaration]
if (dev->power.direct_complete && pm_resume_via_firmware())
^
cc1: some warnings being treated as errors
vim +/pm_resume_via_firmware +936 drivers/base/power/main.c
930 pm_runtime_put(dev);
931 /*
932 * If the device had been runtime-suspended before the system went into
933 * the sleep state it is going out of and it has never been resumed till
934 * now, resume it in case the firmware powered it up.
935 */
> 936 if (dev->power.direct_complete && pm_resume_via_firmware())
937 pm_request_resume(dev);
938 }
939
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Download attachment ".config.gz" of type "application/octet-stream" (20807 bytes)
Powered by blists - more mailing lists