linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] PM / OPP: Export more symbols for module usage
Date: Tue, 8 Jan 2013 14:54:01 +0800	[thread overview]
Message-ID: <1357628043-19256-2-git-send-email-shawn.guo@linaro.org> (raw)
In-Reply-To: <1357628043-19256-1-git-send-email-shawn.guo@linaro.org>

Export opp_init_cpufreq_table and opp_free_cpufreq_table for module
usage.

Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
---
 drivers/base/power/opp.c |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
index 50b2831..d16db9a 100644
--- a/drivers/base/power/opp.c
+++ b/drivers/base/power/opp.c
@@ -661,6 +661,7 @@ int opp_init_cpufreq_table(struct device *dev,
 
 	return 0;
 }
+EXPORT_SYMBOL(opp_init_cpufreq_table);
 
 /**
  * opp_free_cpufreq_table() - free the cpufreq table
@@ -678,6 +679,7 @@ void opp_free_cpufreq_table(struct device *dev,
 	kfree(*table);
 	*table = NULL;
 }
+EXPORT_SYMBOL(opp_free_cpufreq_table);
 #endif		/* CONFIG_CPU_FREQ */
 
 /**
-- 
1.7.9.5

  reply	other threads:[~2013-01-08  6:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  6:54 [PATCH 0/3] Add imx6q-cpufreq driver support Shawn Guo
2013-01-08  6:54 ` Shawn Guo [this message]
2013-01-08 14:47   ` [PATCH 1/3] PM / OPP: Export more symbols for module usage Nishanth Menon
2013-01-08 15:06     ` Shawn Guo
2013-01-08  6:54 ` [PATCH 2/3] cpufreq: add imx6q-cpufreq driver Shawn Guo
2013-01-08  8:57   ` Sascha Hauer
2013-01-08 11:28     ` Shawn Guo
2013-01-08 13:10       ` Shawn Guo
2013-01-08  9:16   ` Viresh Kumar
2013-01-08 14:35     ` Shawn Guo
2013-01-08 14:41       ` Viresh Kumar
2013-01-08 15:04         ` Shawn Guo
2013-01-08 15:19           ` Viresh Kumar
2013-01-09 11:25             ` Viresh Kumar
2013-01-08  6:54 ` [PATCH 3/3] ARM: imx: enable imx6q-cpufreq support Shawn Guo

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=1357628043-19256-2-git-send-email-shawn.guo@linaro.org \
    --to=shawn.guo@linaro.org \
    --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).