1
0
Fork 0

mtd: mark const init data with __initconst instead of __initdata

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: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
hifive-unleashed-5.1
Uwe Kleine-König 2012-03-29 23:12:32 +02:00 committed by David Woodhouse
parent ce4bbeeddb
commit 6d56b9d658
1 changed files with 1 additions and 1 deletions

View File

@ -59,7 +59,7 @@ static struct mtd_partition bigflash_parts[] = {
}
};
static const char *part_probes[] __initdata = {"cmdlinepart", "RedBoot", NULL};
static const char *part_probes[] __initconst = {"cmdlinepart", "RedBoot", NULL};
#define init_sbc82xx_one_flash(map, br, or) \
do { \