[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1467019575-664-2-git-send-email-jszhang@marvell.com>
Date: Mon, 27 Jun 2016 17:26:13 +0800
From: Jisheng Zhang <jszhang@...vell.com>
To: <srinivas.pandruvada@...ux.intel.com>, <lenb@...nel.org>,
<rjw@...ysocki.net>, <viresh.kumar@...aro.org>
CC: <linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Jisheng Zhang <jszhang@...vell.com>
Subject: [PATCH 1/3] intel_pstate: Fix incorrect placement of __initdata
__initdata should be placed between the variable name and equal sign
(if there is) for the variable to be placed in the intended section.
Signed-off-by: Jisheng Zhang <jszhang@...vell.com>
---
drivers/cpufreq/intel_pstate.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
index fe9dc17..44099e9 100644
--- a/drivers/cpufreq/intel_pstate.c
+++ b/drivers/cpufreq/intel_pstate.c
@@ -1574,9 +1574,9 @@ static struct cpufreq_driver intel_pstate_driver = {
.name = "intel_pstate",
};
-static int __initdata no_load;
-static int __initdata no_hwp;
-static int __initdata hwp_only;
+static int no_load __initdata;
+static int no_hwp __initdata;
+static int hwp_only __initdata;
static unsigned int force_load;
static int intel_pstate_msrs_not_valid(void)
--
2.8.1
Powered by blists - more mailing lists