From: kbuild test robot <lkp@intel.com>
To: dbasehore@chromium.org
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
dbasehore@chromium.org, linux-pm@vger.kernel.org,
rjw@rjwysocki.net, pavel@ucw.cz, len.brown@intel.com,
tglx@linutronix.de, gnomes@lxorguk.ukuu.org.uk,
peterz@infradead.org
Subject: Re: [PATCH v3 4/5] freeze: Add error reporting
Date: Thu, 9 Jun 2016 12:14:45 +0800 [thread overview]
Message-ID: <201606091239.F8WiEKuP%fengguang.wu@intel.com> (raw)
In-Reply-To: <1465441738-7972-5-git-send-email-dbasehore@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]
Hi,
[auto build test WARNING on pm/linux-next]
[also build test WARNING on v4.7-rc2 next-20160608]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/dbasehore-chromium-org/Add-suspend-to-idle-validation-for-Intel-SoCs/20160609-111421
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: x86_64-randconfig-s3-06091046 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> drivers/cpuidle/cpuidle.c:37:12: warning: 'cpuidle_freeze_error' defined but not used [-Wunused-variable]
static int cpuidle_freeze_error;
^~~~~~~~~~~~~~~~~~~~
vim +/cpuidle_freeze_error +37 drivers/cpuidle/cpuidle.c
21 #include <linux/module.h>
22 #include <linux/suspend.h>
23 #include <linux/tick.h>
24 #include <trace/events/power.h>
25
26 #include "cpuidle.h"
27
28 DEFINE_PER_CPU(struct cpuidle_device *, cpuidle_devices);
29 DEFINE_PER_CPU(struct cpuidle_device, cpuidle_dev);
30
31 DEFINE_MUTEX(cpuidle_lock);
32 LIST_HEAD(cpuidle_detected_devices);
33
34 static int enabled_devices;
35 static int off __read_mostly;
36 static int initialized __read_mostly;
> 37 static int cpuidle_freeze_error;
38
39 int cpuidle_disabled(void)
40 {
41 return off;
42 }
43 void disable_cpuidle(void)
44 {
45 off = 1;
---
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: 25981 bytes --]
next prev parent reply other threads:[~2016-06-09 4:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 3:08 [PATCH v3 0/5] Add suspend-to-idle validation for Intel SoCs dbasehore
2016-06-09 3:08 ` [PATCH v3 1/5] x86: stub out pmc function dbasehore
2016-06-09 3:08 ` [PATCH v3 2/5] clockevents: Add timed freeze dbasehore
2016-06-09 3:08 ` [PATCH v3 3/5] x86, apic: Add timed freeze support dbasehore
2016-06-09 3:08 ` [PATCH v3 4/5] freeze: Add error reporting dbasehore
2016-06-09 4:14 ` kbuild test robot [this message]
2016-06-09 3:08 ` [PATCH v3 5/5] intel_idle: Add S0ix validation dbasehore
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=201606091239.F8WiEKuP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dbasehore@chromium.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=kbuild-all@01.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).