summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2012-03-30 20:04:56 (GMT)
committerSamuel Ortiz <sameo@linux.intel.com>2012-05-01 10:00:20 (GMT)
commitf4bf7cf4cab90c98fe68a7afa12fb72790fd04bf (patch)
treef4dcc633b6fc440272ca7a74e8261fa527462784
parent69964ea4c7b68c9399f7977aa5b9aa6539a6a98a (diff)
downloadlinux-fsl-qoriq-f4bf7cf4cab90c98fe68a7afa12fb72790fd04bf.tar.xz
mfd: Mark const init data with __initconst instead of __initdata for ab5500
As long as there is no other non-const variable marked __initdata in the same compilation unit it doesn't hurt. If there were one however compilation would fail with error: $variablename causes a section type conflict because a section containing const variables is marked read only and so cannot contain non-const variables. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
-rw-r--r--drivers/mfd/ab5500-core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mfd/ab5500-core.c b/drivers/mfd/ab5500-core.c
index 54d0fe4..3765c76 100644
--- a/drivers/mfd/ab5500-core.c
+++ b/drivers/mfd/ab5500-core.c
@@ -1291,7 +1291,7 @@ struct ab_family_id {
char *name;
};
-static const struct ab_family_id ids[] __initdata = {
+static const struct ab_family_id ids[] __initconst = {
/* AB5500 */
{
.id = AB5500_1_0,