From: kbuild test robot <lkp@intel.com>
To: "Bálint Czobor" <czoborbalint@gmail.com>
Cc: kbuild-all@01.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
"Mike Chan" <mike@android.com>,
"Todd Poynor" <toddpoynor@google.com>,
"Bálint Czobor" <czoborbalint@gmail.com>
Subject: Re: [PATCH 1/1] cpufreq: interactive: New 'interactive' governor
Date: Thu, 29 Oct 2015 05:27:58 +0800 [thread overview]
Message-ID: <201510290533.zaaaAJqP%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446062946-2770-1-git-send-email-czoborbalint@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Hi Mike,
[auto build test ERROR on pm/linux-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/B-lint-Czobor/cpufreq-interactive-New-interactive-governor/20151029-041207
config: i386-allmodconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> drivers/cpufreq/cpufreq_interactive.c:35:46: fatal error: trace/events/cpufreq_interactive.h: No such file or directory
compilation terminated.
vim +35 drivers/cpufreq/cpufreq_interactive.c
29 #include <linux/timer.h>
30 #include <linux/workqueue.h>
31 #include <linux/kthread.h>
32 #include <linux/slab.h>
33
34 #define CREATE_TRACE_POINTS
> 35 #include <trace/events/cpufreq_interactive.h>
36
37 struct cpufreq_interactive_cpuinfo {
38 struct timer_list cpu_timer;
---
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: 51611 bytes --]
next prev parent reply other threads:[~2015-10-28 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 20:09 Bálint Czobor
2015-10-28 21:27 ` kbuild test robot [this message]
2015-10-28 22:05 Bálint Czobor
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=201510290533.zaaaAJqP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=czoborbalint@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mike@android.com \
--cc=rjw@rjwysocki.net \
--cc=toddpoynor@google.com \
--cc=viresh.kumar@linaro.org \
/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®