linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: kbuild test robot <lkp@intel.com>,
	Linux PM <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-all] [PATCH 4/4] thermal/intel_powerclamp: stop sched tick in forced idle
Date: Wed, 30 Nov 2016 05:50:45 +0800	[thread overview]
Message-ID: <20161129215045.GE16489@yexl-desktop> (raw)
In-Reply-To: <20161128231123.24fc63c0@yairi>

On 11/28, Jacob Pan wrote:
>On Tue, 29 Nov 2016 07:21:14 +0800
>kbuild test robot <lkp@intel.com> wrote:
>
>> Hi Jacob,
>> 
>> [auto build test ERROR on soc-thermal/next]
>> [also build test ERROR on v4.9-rc7 next-20161128]
>> [if your patch is applied to the wrong git tree, please drop us a
>> note to help improve the system]
>> 
>This patchset is applicable on top of another patch indicated in the
>cover letter.
>(https://lkml.org/lkml/2016/11/28/683)
>

Thanks for the info, you could try use git(>=2.9.0) format-patch --base=<commit> (or
--base=auto for convenience) to record what (public, well-known) commit
your patch series was built on, then 0day would be able to know the
exact base and prerequisite patches.

Thanks,
Xiaolong

>Thanks,
>
>Jacob
>
>> url:
>> https://github.com/0day-ci/linux/commits/Jacob-Pan/Misc-enhancements-to-intel_powerclamp/20161129-065523
>> base:
>> https://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal.git
>> next config: x86_64-randconfig-x015-201648 (attached as .config)
>> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the
>> attached .config to linux build tree make ARCH=x86_64 
>> 
>> All errors (new ones prefixed by >>):
>> 
>>    drivers/thermal/intel_powerclamp.c: In function
>> 'clamp_idle_injection_func':
>> >> drivers/thermal/intel_powerclamp.c:448:2: error: implicit
>> >> declaration of function
>> >> 'play_idle' [-Werror=implicit-function-declaration]
>>      play_idle(jiffies_to_msecs(w_data->duration_jiffies));
>>      ^~~~~~~~~
>>    cc1: some warnings being treated as errors
>> 
>> vim +/play_idle +448 drivers/thermal/intel_powerclamp.c
>> 
>>    442			smp_mb();
>>    443		}
>>    444	
>>    445		if (should_skip)
>>    446			goto balance;
>>    447	
>>  > 448
>>  > play_idle(jiffies_to_msecs(w_data->duration_jiffies));
>>    449	
>>    450	balance:
>>    451		if (clamping && w_data->clamping &&
>> cpu_online(w_data->cpu))
>> 
>> ---
>> 0-DAY kernel test infrastructure                Open Source
>> Technology Center
>> https://lists.01.org/pipermail/kbuild-all                   Intel
>> Corporation
>
>[Jacob Pan]
>_______________________________________________
>kbuild-all mailing list
>kbuild-all@lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all

  reply	other threads:[~2016-11-30  5:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 21:44 [PATCH 0/4] Misc enhancements to intel_powerclamp Jacob Pan
2016-11-28 21:44 ` [PATCH 1/4] thermal/intel_powerclamp: Remove duplicated code that starts the kthread Jacob Pan
2016-11-28 21:44 ` [PATCH 2/4] thermal/intel_powerclamp: Convert the kthread to kthread worker API Jacob Pan
2016-11-28 21:44 ` [PATCH 3/4] thermal/intel_powerclamp: Convert to CPU hotplug state Jacob Pan
2016-11-28 21:44 ` [PATCH 4/4] thermal/intel_powerclamp: stop sched tick in forced idle Jacob Pan
2016-11-28 23:21   ` kbuild test robot
2016-11-29  7:11     ` Jacob Pan
2016-11-29 21:50       ` Ye Xiaolong [this message]
2016-11-28 23:14 ` [PATCH 0/4] Misc enhancements to intel_powerclamp 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=20161129215045.GE16489@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkp@intel.com \
    /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).