Uwe Kleine-König 4a043d79dc mips: 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> Cc: linux-mips@linux-mips.org Cc: linux-mips@linux-mips.org Cc: linux-kernel@vger.kernel.org Cc: kernel@pengutronix.de Patchwork: https://patchwork.linux-mips.org/patch/3565/ Signed-off-by: Ralf Baechle <ralf@linux-mips.org>		2012-07-19 11:23:43 +02:00
..
asic-calliope.c	mips: mark const init data with __initconst instead of __initdata	2012-07-19 11:23:43 +02:00
asic-cronus.c	mips: mark const init data with __initconst instead of __initdata	2012-07-19 11:23:43 +02:00
asic-gaia.c	mips: mark const init data with __initconst instead of __initdata	2012-07-19 11:23:43 +02:00
asic-zeus.c	mips: mark const init data with __initconst instead of __initdata	2012-07-19 11:23:43 +02:00
asic_devices.c
asic_int.c
irq_asic.c
Makefile	MIPS: Remove all -Wall and almost all -Werror usage from arch/mips.	2012-05-21 15:09:36 +01:00
prealloc-calliope.c
prealloc-cronus.c
prealloc-cronuslite.c
prealloc-gaia.c
prealloc-zeus.c
prealloc.h