From: kbuild test robot <lkp@intel.com>
To: Lianwei Wang <lianwei.wang@gmail.com>
Cc: kbuild-all@01.org, mingo@kernel.org, rjw@rjwysocki.net,
daniel.lezcano@linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lianwei Wang <lianwei.wang@gmail.com>
Subject: Re: [PATCH] smp: make wake up idle cpus more generic
Date: Thu, 31 Mar 2016 16:24:47 +0800 [thread overview]
Message-ID: <201603311622.dg3lPX4F%fengguang.wu@intel.com> (raw)
In-Reply-To: <1459410795-5693-1-git-send-email-lianwei.wang@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
Hi Lianwei,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.6-rc1 next-20160331]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Lianwei-Wang/smp-make-wake-up-idle-cpus-more-generic/20160331-155548
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: i386-randconfig-n0-201613 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings (new ones prefixed by >>):
drivers/cpuidle/cpuidle.c: In function 'cpuidle_latency_notify':
>> drivers/cpuidle/cpuidle.c:623:37: error: expected ')' before ';' token
wake_up_idle_cpus((cpu_online_mask);
^
>> drivers/cpuidle/cpuidle.c:625:1: error: expected ';' before '}' token
}
^
>> drivers/cpuidle/cpuidle.c:625:1: warning: no return statement in function returning non-void [-Wreturn-type]
vim +623 drivers/cpuidle/cpuidle.c
617 * and then recalculate a new suitable C-state. Just do a cross-cpu IPI; that
618 * wakes them all right up.
619 */
620 static int cpuidle_latency_notify(struct notifier_block *b,
621 unsigned long l, void *v)
622 {
> 623 wake_up_idle_cpus((cpu_online_mask);
624 return NOTIFY_OK;
> 625 }
626
627 static struct notifier_block cpuidle_latency_notifier = {
628 .notifier_call = cpuidle_latency_notify,
---
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: 21634 bytes --]
next prev parent reply other threads:[~2016-03-31 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 7:53 Lianwei Wang
2016-03-31 8:24 ` kbuild test robot [this message]
2016-04-01 5:40 ` Lianwei Wang
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=201603311622.dg3lPX4F%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=kbuild-all@01.org \
--cc=lianwei.wang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rjw@rjwysocki.net \
/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®