From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: [PATCH 2/4] cpufreq: OMAP: remove unused <plat/omap-pm.h>
Date: Wed, 3 Oct 2012 16:00:27 -0700 [thread overview]
Message-ID: <1349305229-28480-3-git-send-email-khilman@deeprootsystems.com> (raw)
In-Reply-To: <1349305229-28480-1-git-send-email-khilman@deeprootsystems.com>
From: Kevin Hilman <khilman@ti.com>
The <plat/*.h> headers are going away, and this one is not used. remove it.
Signed-off-by: Kevin Hilman <khilman@ti.com>
---
drivers/cpufreq/omap-cpufreq.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/cpufreq/omap-cpufreq.c b/drivers/cpufreq/omap-cpufreq.c
index 0fe395a..7d4d455 100644
--- a/drivers/cpufreq/omap-cpufreq.c
+++ b/drivers/cpufreq/omap-cpufreq.c
@@ -31,7 +31,6 @@
#include <asm/cpu.h>
#include <plat/clock.h>
-#include <plat/omap-pm.h>
#include <plat/common.h>
#include <plat/omap_device.h>
--
1.7.9.2
next prev parent reply other threads:[~2012-10-03 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 23:00 [PATCH 0/4] cpufreq: OMAP: fixes for v3.7-rc2 Kevin Hilman
2012-10-03 23:00 ` [PATCH 1/4] cpufreq: OMAP: ensure valid clock rate before scaling Kevin Hilman
2012-10-03 23:00 ` Kevin Hilman [this message]
2012-10-03 23:00 ` [PATCH 3/4] cpufreq: OMAP: fix clock usage to be SoC independent, remove plat/ includes Kevin Hilman
2012-10-03 23:00 ` [PATCH 4/4] cpufreq: OMAP: use get_cpu_device() instead of omap_device API Kevin Hilman
2012-10-07 20:13 ` [PATCH 0/4] cpufreq: OMAP: fixes for v3.7-rc2 Rafael J. Wysocki
2012-10-08 21:36 ` Kevin Hilman
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=1349305229-28480-3-git-send-email-khilman@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 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).