From: Paul Bolle <pebolle@tiscali.nl>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kevin Hilman <khilman@linaro.org>
Subject: Re: linux-next: build warning after merge of the pm tree
Date: Mon, 17 Nov 2014 12:31:43 +0100 [thread overview]
Message-ID: <1416223903.22252.11.camel@x220> (raw)
In-Reply-To: <20141117134414.7f4d8d21@canb.auug.org.au>
On Mon, 2014-11-17 at 13:44 +1100, Stephen Rothwell wrote:
> Hi Rafael,
>
> After merging the pm tree, today's linux-next build (arm multi_v7_defconfig)
> produced this warning:
>
> kernel/power/Kconfig:132:error: recursive dependency detected!
> kernel/power/Kconfig:132: symbol PM_RUNTIME is selected by PM_GENERIC_DOMAINS
> kernel/power/Kconfig:272: symbol PM_GENERIC_DOMAINS is selected by PM_RUNTIME
>
> Caused by commit 9cdd5fd742e6 ("PM / domains: Kconfig: always enable
> PM_RUNTIME when genpd enabled").
This error also popped up when I fiddled with omap2plus_defconfig on top
of next-20141117. Note that I ended up with a .config which has
CONFIG_ARCH_MULTI_V7 set. The error appears to be triggered by the
Kconfig entry for ARCH_EXYNOS (in arch/arm/mach-exynos/Kconfig). It
contains
select PM_GENERIC_DOMAINS if PM_RUNTIME
(Perhaps the :272: line needs rephrasing in the error Stephen quoted. It
confused me quite a bit.)
Naively dropping that select statement from ARCH_EXYNOS triggered yet
another error:
kernel/power/Kconfig:145:error: recursive dependency detected!
kernel/power/Kconfig:145: symbol PM depends on PM_RUNTIME
kernel/power/Kconfig:132: symbol PM_RUNTIME is selected by PM_GENERIC_DOMAINS
kernel/power/Kconfig:272: symbol PM_GENERIC_DOMAINS is selected by PM
After that I admitted defeat.
Paul Bolle
next prev parent reply other threads:[~2014-11-17 11:31 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 2:44 linux-next: build warning after merge of the pm tree Stephen Rothwell
2014-11-17 11:31 ` Paul Bolle [this message]
2014-11-17 23:14 ` Rafael J. Wysocki
2014-11-17 23:45 ` Paul Bolle
2014-11-18 0:34 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 5:00 Stephen Rothwell
2024-02-05 5:30 ` Meng, Li (Jassmine)
2022-02-06 22:40 Stephen Rothwell
2021-10-13 6:28 Stephen Rothwell
2022-01-17 22:02 ` Stephen Rothwell
2021-03-31 0:29 Stephen Rothwell
2021-03-31 6:22 ` Vitaly Kuznetsov
2021-04-02 17:18 ` Rafael J. Wysocki
2021-02-15 0:39 Stephen Rothwell
2021-02-15 0:39 ` Stephen Rothwell
2021-02-15 10:23 ` Andy Shevchenko
2021-02-15 10:23 ` Andy Shevchenko
2021-02-15 10:24 ` Andy Shevchenko
2021-02-15 10:24 ` Andy Shevchenko
2021-02-22 8:34 ` Stephen Rothwell
2021-02-22 8:34 ` Stephen Rothwell
2021-01-27 1:43 Stephen Rothwell
2021-01-27 3:54 ` Zhang Rui
2020-11-19 0:09 Stephen Rothwell
2020-11-19 16:22 ` Andy Shevchenko
2020-09-22 8:11 Stephen Rothwell
2020-10-01 9:43 ` Stephen Rothwell
2020-10-08 9:35 ` Stephen Rothwell
2020-10-15 7:20 ` Stephen Rothwell
2020-07-30 2:55 Stephen Rothwell
2020-07-30 3:10 ` Neal Liu
2020-01-19 23:40 Stephen Rothwell
2019-10-14 23:08 Stephen Rothwell
2019-10-15 8:23 ` Andy Shevchenko
2019-10-15 9:41 ` Rafael J. Wysocki
[not found] <201907111346291954773@zte.com.cn>
2019-07-11 12:26 ` Rafael J. Wysocki
2019-07-11 1:31 Stephen Rothwell
2019-01-23 23:45 Stephen Rothwell
2018-07-30 2:00 Stephen Rothwell
2018-07-30 7:24 ` Sakari Ailus
2018-07-30 7:30 ` jacopo mondi
2018-07-31 0:39 ` Stephen Rothwell
2018-06-08 0:30 Stephen Rothwell
2018-06-08 9:14 ` Rafael J. Wysocki
2018-04-09 1:24 Stephen Rothwell
2018-04-10 7:05 ` Rafael J. Wysocki
2016-11-13 23:40 Stephen Rothwell
2016-11-14 0:03 ` Rafael J. Wysocki
2016-11-14 8:49 ` Akshay Adiga
2014-10-29 2:51 Stephen Rothwell
2014-10-29 14:55 ` Rafael J. Wysocki
2014-10-29 15:23 ` Fengguang Wu
2014-10-29 15:56 ` 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=1416223903.22252.11.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.