Thread (5 messages) 5 messages, 1 author, 2012-03-30

Re: [PATCH 00/17] mark const init data with __initconst instead of __initdata

From: Uwe Kleine-König <hidden>
Date: 2012-03-30 10:00:01
Also in: linux-arm-msm, linux-hams, linux-ide, linux-mips, linux-mm, linux-omap, linux-samsung-soc, netdev, platform-driver-x86

On Thu, Mar 29, 2012 at 11:11:31PM +0200, Uwe Kleine-König wrote:
Hello,

this series fixes a common error to use __initdata to mark const
variables. Most of the time this works well enough to go unnoticed
(though I wonder why the linker doesn't warn about that).
Just try adding something like

	int something __initdata;

to one of the patched files and compile to see the error.

While touching these annotations I also corrected the position where it
was wrong to go between the variable name and the =.

Note this series is not compile tested.
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.

I will send a fixed series later today.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help