Jan Beulich
2009-Feb-03 15:52 UTC
[Xen-devel] [PATCH] attach __exit to the (unused) cpufreq governor exit handlers
... in order to make them disappear from the final image. Of course
they could as well be removed altogether, but I assumed that whoever
added them had a reason to do so.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
--- 2009-01-30.orig/xen/drivers/cpufreq/cpufreq_misc_governors.c 2008-12-17
16:52:27.000000000 +0100
+++ 2009-01-30/xen/drivers/cpufreq/cpufreq_misc_governors.c 2009-01-30
14:05:08.000000000 +0100
@@ -61,7 +61,7 @@ static int __init cpufreq_gov_userspace_
}
__initcall(cpufreq_gov_userspace_init);
-static void cpufreq_gov_userspace_exit(void)
+static void __exit cpufreq_gov_userspace_exit(void)
{
cpufreq_unregister_governor(&cpufreq_gov_userspace);
}
@@ -106,7 +106,7 @@ static int __init cpufreq_gov_performanc
}
__initcall(cpufreq_gov_performance_init);
-static void cpufreq_gov_performance_exit(void)
+static void __exit cpufreq_gov_performance_exit(void)
{
cpufreq_unregister_governor(&cpufreq_gov_performance);
}
@@ -151,7 +151,7 @@ static int __init cpufreq_gov_powersave_
}
__initcall(cpufreq_gov_powersave_init);
-static void cpufreq_gov_powersave_exit(void)
+static void __exit cpufreq_gov_powersave_exit(void)
{
cpufreq_unregister_governor(&cpufreq_gov_powersave);
}
--- 2009-01-30.orig/xen/drivers/cpufreq/cpufreq_ondemand.c 2009-01-30
13:54:16.000000000 +0100
+++ 2009-01-30/xen/drivers/cpufreq/cpufreq_ondemand.c 2009-01-30
14:04:51.000000000 +0100
@@ -333,7 +333,7 @@ static int __init cpufreq_gov_dbs_init(v
}
__initcall(cpufreq_gov_dbs_init);
-static void cpufreq_gov_dbs_exit(void)
+static void __exit cpufreq_gov_dbs_exit(void)
{
cpufreq_unregister_governor(&cpufreq_gov_dbs);
}
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel