From: Peter Zijlstra <peterz@infradead.org>
To: kbuild test robot <lkp@intel.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: [tip:sched/core 24/27] kernel/power/suspend.c:431:10: error: implicit declaration of function 'suspend_disable_secondary_cpus'
Date: Fri, 3 May 2019 18:04:58 +0200 [thread overview]
Message-ID: <20190503160458.GF2606@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <201905032053.KmG848Ye%lkp@intel.com>
On Fri, May 03, 2019 at 08:34:57PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
> head: 65874bd36e6ae3028539e989bfb5c28ad457368e
> commit: c2cb30bfceceba8a2a0d5713230a250dd6140e22 [24/27] power/suspend: Add function to disable secondaries for suspend
> config: x86_64-randconfig-l3-05031806 (attached as .config)
> compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
> reproduce:
> git checkout c2cb30bfceceba8a2a0d5713230a250dd6140e22
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
The below appears to fix.
--- a/include/linux/cpu.h
+++ b/include/linux/cpu.h
@@ -150,6 +150,8 @@ static inline void suspend_enable_second
#else /* !CONFIG_PM_SLEEP_SMP */
static inline int disable_nonboot_cpus(void) { return 0; }
static inline void enable_nonboot_cpus(void) {}
+static inline int suspend_disable_secondary_cpus(void) { return 0; }
+static inline void suspend_enable_secondary_cpus(void) { }
#endif /* !CONFIG_PM_SLEEP_SMP */
void cpu_startup_entry(enum cpuhp_state state);
next prev parent reply other threads:[~2019-05-03 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 12:34 kbuild test robot
2019-05-03 16:04 ` Peter Zijlstra [this message]
2019-05-03 23:51 ` Nicholas Piggin
2019-05-04 0:50 ` Ingo Molnar
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=20190503160458.GF2606@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=tipbuild@zytor.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
Powered by JetHome