From: kbuild test robot <lkp@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: kbuild-all@01.org, Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [RFC][PATCH 2/2] PM / sleep: Kick devices that might have been reset by firmware
Date: Wed, 30 Sep 2015 08:36:00 +0800 [thread overview]
Message-ID: <201509300812.KVdM5pN3%fengguang.wu@intel.com> (raw)
In-Reply-To: <5732365.XVsXxYIbHS@vostro.rjw.lan>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
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
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 20807 bytes --]
next prev parent reply other threads:[~2015-09-30 0:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 0:46 [RFC][PATCH 0/2] PM / sleep: Make it possible to check if suspend/resume goes via firmware Rafael J. Wysocki
2015-09-30 0:52 ` [RFC][PATCH 1/2] PM / sleep: Add flags to indicate platform firmware involvement Rafael J. Wysocki
2015-09-30 0:53 ` [RFC][PATCH 2/2] PM / sleep: Kick devices that might have been reset by firmware Rafael J. Wysocki
2015-09-30 0:36 ` kbuild test robot [this message]
2015-09-30 14:46 ` Alan Stern
2015-09-30 21:51 ` Rafael J. Wysocki
2015-10-01 14:47 ` Alan Stern
2015-10-01 22:13 ` Rafael J. Wysocki
2015-10-02 1:50 ` [RFC][PATCH v2 0/2] PM / sleep: Make it possible to check if suspend/resume goes via firmware Rafael J. Wysocki
2015-10-02 1:52 ` [RFC][PATCH v2 1/2] PM / sleep: Add flags to indicate platform firmware involvement Rafael J. Wysocki
2015-10-02 1:54 ` [RFC][PATCH v2 2/2] PM / PCI / ACPI: Kick devices that might have been reset by firmware Rafael J. Wysocki
2015-10-06 22:48 ` [PATCH v3 0/3] PM / sleep: Make it possible to check if suspend/resume goes via firmware Rafael J. Wysocki
2015-10-06 22:49 ` [PATCH v3 1/3] PM / sleep: Add flags to indicate platform firmware involvement Rafael J. Wysocki
2015-10-06 22:50 ` [PATCH v3 2/3] PM / PCI / ACPI: Kick devices that might have been reset by firmware Rafael J. Wysocki
2015-10-06 22:53 ` [RFC][PATCH v3 3/3] input: i8042: Avoid resetting controller on system suspend/resume Rafael J. Wysocki
2015-10-06 22:34 ` Dmitry Torokhov
2015-10-06 23:08 ` Rafael J. Wysocki
2015-10-06 22:43 ` Dmitry Torokhov
2015-10-06 23:31 ` Rafael J. Wysocki
2015-10-06 23:11 ` kbuild test robot
2015-10-06 23:26 ` Dmitry Torokhov
2015-10-06 23:44 ` Rafael J. Wysocki
2015-10-07 1:03 ` [Update][PATCH " Rafael J. Wysocki
2015-10-12 20:17 ` Rafael J. Wysocki
2015-10-12 20:11 ` Dmitry Torokhov
2015-10-12 20:41 ` Rafael J. Wysocki
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=201509300812.KVdM5pN3%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.