From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] cpuidle: move ARCH_NEEDS_CPU_IDLE_COUPLED Kconfig option
Date: Fri, 07 Jun 2013 12:53:13 +0200 [thread overview]
Message-ID: <7104482.Ecl7mMk8ke@wuerfel> (raw)
In-Reply-To: <51AF3424.5060200@linaro.org>
On Wednesday 05 June 2013 14:50:44 Daniel Lezcano wrote:
>
> IMHO, this option depends on CPU_IDLE and thus must be kept inside the
> CPU_IDLE menuconfig.
>
> The warning raised here is because this option is selected by the arch
> Kconfig without checking if CPU_IDLE is set or not.
>
> I am in favor to change the OMAP / TEGRA Kconfigs instead, in this way:
Fine with me as well.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpuidle: move ARCH_NEEDS_CPU_IDLE_COUPLED Kconfig option
Date: Fri, 07 Jun 2013 12:53:13 +0200 [thread overview]
Message-ID: <7104482.Ecl7mMk8ke@wuerfel> (raw)
In-Reply-To: <51AF3424.5060200@linaro.org>
On Wednesday 05 June 2013 14:50:44 Daniel Lezcano wrote:
>
> IMHO, this option depends on CPU_IDLE and thus must be kept inside the
> CPU_IDLE menuconfig.
>
> The warning raised here is because this option is selected by the arch
> Kconfig without checking if CPU_IDLE is set or not.
>
> I am in favor to change the OMAP / TEGRA Kconfigs instead, in this way:
Fine with me as well.
Arnd
next prev parent reply other threads:[~2013-06-07 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 12:38 [PATCH] cpuidle: move ARCH_NEEDS_CPU_IDLE_COUPLED Kconfig option Arnd Bergmann
2013-06-05 12:38 ` Arnd Bergmann
2013-06-05 12:50 ` Daniel Lezcano
2013-06-05 12:50 ` Daniel Lezcano
2013-06-05 20:36 ` Rafael J. Wysocki
2013-06-05 20:36 ` Rafael J. Wysocki
2013-06-07 10:53 ` Arnd Bergmann [this message]
2013-06-07 10:53 ` Arnd Bergmann
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=7104482.Ecl7mMk8ke@wuerfel \
--to=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.