mfd: Mark const init data with __initconst instead of __initdata for ab5500
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>
Fri, 30 Mar 2012 20:04:56 +0000 (22:04 +0200)
committerSamuel Ortiz <sameo@linux.intel.com>
Tue, 1 May 2012 10:00:20 +0000 (12:00 +0200)
commitf4bf7cf4cab90c98fe68a7afa12fb72790fd04bf
treef4dcc633b6fc440272ca7a74e8261fa527462784
parent69964ea4c7b68c9399f7977aa5b9aa6539a6a98a
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>
drivers/mfd/ab5500-core.c