Messages in this thread | | | From | Andreas Schwab <> | Subject | Re: [PATCH 00/17] mark const init data with __initconst instead of __initdata | Date | Fri, 30 Mar 2012 13:37:26 +0200 |
| |
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:
> After a question by Shawn Guo I noticed that my command to do the changes > was to lax and changed things that must not be changed (at least not > with further care). Affected are lines like: > > static const char *at91_dt_board_compat[] __initconst = { > > While at91_dt_board_compat[0] is const, at91_dt_board_compat is not.
Though it looks like at91_dt_board_compat should really be const (it is assigned to a const pointer, likewise for all other uses of struct machine_desc.dt_compat).
Andreas.
-- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |