From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: fix CONFIG_CPU_IDLE dependency on CONFIG_PM
Date: Fri, 29 Jun 2012 06:04:08 -0700 [thread overview]
Message-ID: <20120629130407.GF4202@atomide.com> (raw)
In-Reply-To: <1340901914-771-1-git-send-email-khilman@ti.com>
* Kevin Hilman <khilman@ti.com> [120628 09:49]:
> commit 164e0cbf60 (ARM: OMAP3/4: consolidate cpuidle Makefile) added
> an OMAP-specific dependency from CPU_IDLE to CONFIG_PM. This causes
> some randconfig warnings when CONFIG_PM has unmet dependencies:
>
> warning: (ARCH_OMAP3 && ARCH_OMAP4) selects PM which has unmet direct dependencies (PM_SLEEP || PM_RUNTIME)
> warning: (ARCH_OMAP3 && ARCH_OMAP4) selects PM which has unmet direct dependencies (PM_SLEEP || PM_RUNTIME)
> warning: (ARCH_OMAP3 && ARCH_OMAP4) selects PM which has unmet direct dependencies (PM_SLEEP || PM_RUNTIME)
>
> Fix this by making the dependency on CONFIG_PM_RUNTIME (which in turn
> will enable CONFIG_PM.)
>
> Reported-by: Tony Lindgren <tony@atomide.com>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Signed-off-by: Kevin Hilman <khilman@ti.com>
> ---
> Tony, this fixes the randconfig problems you mentioned. It applies on
> top of your testing-board branch, where the commit that introduced this
> problem is applied.
Thanks applying into fixes-non-critical. The warning is there already in
fixes-non-critical, testing-board was just based on that.
Tony
prev parent reply other threads:[~2012-06-29 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 16:45 [PATCH] ARM: OMAP2+: fix CONFIG_CPU_IDLE dependency on CONFIG_PM Kevin Hilman
2012-06-29 13:04 ` Tony Lindgren [this message]
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=20120629130407.GF4202@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).