From: Shawn Guo <shawn.guo@freescale.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Mark Brown <broonie@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Nishanth Menon <nm@ti.com>, Rob Herring <robh@kernel.org>,
Simon Horman <horms+renesas@verge.net.au>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-pm@vger.kernel.org
Subject: Re: PM / OPP: ARCH_HAS_OPP
Date: Tue, 29 Jul 2014 15:03:46 +0800 [thread overview]
Message-ID: <20140729070345.GA24750@dragon> (raw)
In-Reply-To: <1406551632.5397.17.camel@x220>
On Mon, Jul 28, 2014 at 02:47:12PM +0200, Paul Bolle wrote:
> Mark,
>
> Your commit 78c5e0bb145d ("PM / OPP: Remove ARCH_HAS_OPP") landed in
> today's linux-next (ie, next-20140728). It removes the Kconfig symbol
> ARCH_HAS_OPP and ten select statements for that symbol.
>
> After that commit there are still nine select statements for that symbol
> left in linux-next. (These select statements are now actually NOPs.) The
> peculiar thing is that these nine statements are all found in Kconfig
> files also touched by that commit.
>
> Anyhow, are patches to remove these pointless select statements queued
> somewhere?
There a couple of such select in imx Kconfig, and I will clean them up.
Shawn
next prev parent reply other threads:[~2014-07-29 7:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 12:47 PM / OPP: ARCH_HAS_OPP Paul Bolle
2014-07-29 7:03 ` Shawn Guo [this message]
2014-09-12 8:38 ` [PATCH] PM / OPP: Remove ARCH_HAS_OPP completely Paul Bolle
2014-09-12 8:38 ` Paul Bolle
2014-09-12 8:38 ` Paul Bolle
2014-09-12 10:20 ` Nishanth Menon
2014-09-12 10:20 ` Nishanth Menon
2014-09-12 10:20 ` Nishanth Menon
2014-09-12 10:46 ` Paul Bolle
2014-09-12 10:46 ` Paul Bolle
2014-09-12 10:46 ` Paul Bolle
2014-09-12 11:03 ` Geert Uytterhoeven
2014-09-12 11:03 ` Geert Uytterhoeven
2014-09-12 11:03 ` Geert Uytterhoeven
2014-09-12 11:14 ` Paul Bolle
2014-09-12 11:14 ` Paul Bolle
2014-09-12 11:14 ` Paul Bolle
2014-09-16 0:09 ` Simon Horman
2014-09-16 0:09 ` Simon Horman
2014-09-16 0:09 ` Simon Horman
2014-09-16 0:23 ` Simon Horman
2014-09-16 0:23 ` Simon Horman
2014-09-16 0:23 ` Simon Horman
2014-09-23 8:08 ` [PATCH] ARM: shmobile: " Paul Bolle
2014-09-23 8:08 ` Paul Bolle
2014-09-23 8:08 ` Paul Bolle
2014-09-23 8:27 ` Geert Uytterhoeven
2014-09-23 8:27 ` Geert Uytterhoeven
2014-09-23 8:27 ` Geert Uytterhoeven
2014-09-24 0:36 ` Simon Horman
2014-09-24 0:36 ` Simon Horman
2014-09-24 0:36 ` Simon Horman
2014-09-23 8:14 ` [PATCH] PM / devfreq: " Paul Bolle
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=20140729070345.GA24750@dragon \
--to=shawn.guo@freescale.com \
--cc=broonie@linaro.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=pebolle@tiscali.nl \
--cc=rafael.j.wysocki@intel.com \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.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 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.