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>
This commit is contained in:
parent
69964ea4c7
commit
f4bf7cf4ca
1 changed files with 1 additions and 1 deletions
|
@ -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,
|
||||
|
|
Loading…
Reference in a new issue