From: Jean Pihet <jean.pihet@newoldbits.com>
To: Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Mark Gross <markgross@thegnar.org>,
Venkatesh Pallipadi <venki@google.com>
Cc: Jean Pihet <j-pihet@ti.com>
Subject: [PATCH 0/2] PM / QoS: unconditionally build the feature
Date: Tue, 7 Feb 2012 09:34:04 +0100 [thread overview]
Message-ID: <1328603646-2714-1-git-send-email-j-pihet@ti.com> (raw)
The PM QoS features depend on CONFIG_PM which depends on
PM_SLEEP || PM_RUNTIME. This breaks CPU C-states with kernels
not having these CONFIGs.
Those patches allow the features in all cases.
Based on 3.3-rc1 from mainline.
Tested on OMAP3 Beagleboard, with CONFIG_PM.
Compile tested using the i386 defconfig, with and without CONFIG_PM.
Jean Pihet (2):
PM / QoS: unconditionally build the feature
PM / QoS: unconditionally build the per-device constraints feature
drivers/base/power/Makefile | 3 +-
include/linux/pm_qos.h | 66 -------------------------------------------
kernel/power/Makefile | 3 +-
3 files changed, 4 insertions(+), 68 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-02-07 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 8:34 Jean Pihet [this message]
2012-02-07 8:34 ` [PATCH 1/2] PM / QoS: unconditionally build the feature Jean Pihet
2012-02-12 2:06 ` mark gross
2012-02-12 21:37 ` Rafael J. Wysocki
2012-02-13 13:50 ` [PATCH] " Jean Pihet
2012-02-13 15:41 ` Rafael J. Wysocki
2012-02-13 15:40 ` Jean Pihet
2012-02-17 19:27 ` [linux-pm] " Pavel Machek
2012-02-17 20:48 ` Rafael J. Wysocki
2012-02-07 8:34 ` [PATCH 2/2] PM / QoS: unconditionally build the per-device constraints feature Jean Pihet
2012-02-12 2:07 ` mark gross
2012-02-12 21:27 ` Rafael J. Wysocki
2012-02-15 15:33 ` mark gross
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=1328603646-2714-1-git-send-email-j-pihet@ti.com \
--to=jean.pihet@newoldbits.com \
--cc=j-pihet@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=rjw@sisk.pl \
--cc=venki@google.com \
/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).