From: Scott Wood <oss@buserror.net>
To: linuxppc-dev@lists.ozlabs.org
Cc: Tang Yuantian <Yuantian.Tang@feescale.com>,
jwboyer@linux.vnet.ibm.com, mporter@kernel.crashing.org,
chenhui zhao <chenhui.zhao@freescale.com>
Subject: Re: [scottwood:next 14/16] warning: (PPC_PSERIES && ..) selects HOTPLUG_CPU which has unmet direct dependencies (SMP && ..))
Date: Sat, 05 Mar 2016 16:33:37 -0600 [thread overview]
Message-ID: <1457217217.5360.106.camel@buserror.net> (raw)
In-Reply-To: <201603052223.m2Exz413%fengguang.wu@intel.com>
On Sat, 2016-03-05 at 22:37 +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/scottwood/linux next
> head: ea6370d23c919127b2cd204af213223a89457477
> commit: 2f4f1f815bc6d03ea42d4f67dd1e284525e7524e [14/16] powerpc/mpc85xx:
> Add hotplug support on E5500 and E500MC cores
> config: powerpc-iss476-smp_defconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp
> -tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 2f4f1f815bc6d03ea42d4f67dd1e284525e7524e
> # save the attached .config to linux build tree
> make.cross ARCH=powerpc
>
> All warnings (new ones prefixed by >>):
>
> warning: (PPC_PSERIES && PM_SLEEP_SMP) selects HOTPLUG_CPU which has unmet
> direct dependencies (SMP && (PPC_PSERIES || PPC_PMAC || PPC_POWERNV ||
> FSL_SOC_BOOKE))
I see this with the attached config without the above commit, or anything else
I've pushed. I see it with vanilla v4.4, v4.0, v3.0...
I guess it's flagged because the list of dependencies changed, but it's a 4xx
problem, not FSL. 4xx should not claim that suspend/hibernate is possible
with SMP, unless it supports CPU hotplug.
-Scott
parent reply other threads:[~2016-03-05 22:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201603052223.m2Exz413%fengguang.wu@intel.com>]
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=1457217217.5360.106.camel@buserror.net \
--to=oss@buserror.net \
--cc=Yuantian.Tang@feescale.com \
--cc=chenhui.zhao@freescale.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mporter@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).