Messages in this thread | | | Date | Fri, 30 Mar 2012 20:19:36 +0200 | From | Uwe Kleine-König <> | Subject | Re: [PATCH 00/17] mark const init data with __initconst instead of __initdata |
| |
Hello Andreas,
On Fri, Mar 30, 2012 at 01:37:26PM +0200, Andreas Schwab wrote: > 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). Yeah, still for this series I will revert to static const char *at91_dt_board_compat[] __initdata to only have a single logical change.
Thanks Uwe
-- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | -- 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/
| |