From: kbuild test robot <lkp@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: kbuild-all@01.org, daniel.lezcano@linaro.org,
Mathieu Poirier <mathieu.poirier@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Allison Randal <allison@lohutok.net>,
Thomas Gleixner <tglx@linutronix.de>,
Amit Kucheria <amit.kucheria@linaro.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jiri Kosina <jkosina@suse.cz>,
Nicholas Piggin <npiggin@gmail.com>,
"open list:POWER MANAGEMENT CORE" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 2/3] cpuidle: play_idle: Specify play_idle with an idle state
Date: Thu, 3 Oct 2019 19:07:37 +0800 [thread overview]
Message-ID: <201910031923.5ec11w82%lkp@intel.com> (raw)
In-Reply-To: <20191003084242.8655-2-daniel.lezcano@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2455 bytes --]
Hi Daniel,
I love your patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[cannot apply to v5.4-rc1 next-20191003]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Daniel-Lezcano/cpuidle-play_idle-Make-play_idle-more-flexible/20191003-171142
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
Note: the linux-review/Daniel-Lezcano/cpuidle-play_idle-Make-play_idle-more-flexible/20191003-171142 HEAD 67d70fb96ed26998f13be3c91ed6cc5440390408 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
drivers/powercap/idle_inject.c: In function 'idle_inject_fn':
>> drivers/powercap/idle_inject.c:142:5: error: implicit declaration of function 'cpuidle_find_deepest_state'; did you mean 'cpu_report_state'? [-Werror=implicit-function-declaration]
cpuidle_find_deepest_state());
^~~~~~~~~~~~~~~~~~~~~~~~~~
cpu_report_state
cc1: some warnings being treated as errors
vim +142 drivers/powercap/idle_inject.c
120
121 /**
122 * idle_inject_fn - idle injection work function
123 * @cpu: the CPU owning the task
124 *
125 * This function calls play_idle() to inject a specified amount of CPU idle
126 * time.
127 */
128 static void idle_inject_fn(unsigned int cpu)
129 {
130 struct idle_inject_device *ii_dev;
131 struct idle_inject_thread *iit;
132
133 ii_dev = per_cpu(idle_inject_device, cpu);
134 iit = per_cpu_ptr(&idle_inject_thread, cpu);
135
136 /*
137 * Let the smpboot main loop know that the task should not run again.
138 */
139 iit->should_run = 0;
140
141 play_idle(READ_ONCE(ii_dev->idle_duration_us),
> 142 cpuidle_find_deepest_state());
143 }
144
---
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: 69540 bytes --]
next prev parent reply other threads:[~2019-10-03 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 8:42 [PATCH V2 1/3] cpuidle: play_idle: Make play_idle more flexible Daniel Lezcano
2019-10-03 8:42 ` [PATCH V2 2/3] cpuidle: play_idle: Specify play_idle with an idle state Daniel Lezcano
2019-10-03 11:03 ` kbuild test robot
2019-10-03 11:07 ` kbuild test robot [this message]
2019-10-03 8:42 ` [PATCH V2 3/3] powercap/drivers/idle_inject: Specify the idle state to inject Daniel Lezcano
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=201910031923.5ec11w82%lkp@intel.com \
--to=lkp@intel.com \
--cc=allison@lohutok.net \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--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
all inboxes | Powered by JetHome®