Re: [PATCH #upstream] libata: implement libata.force module parameter

From: Tejun Heo
Date: Fri Feb 08 2008 - 06:02:17 EST


Sam Ravnborg wrote:
> I have lost the actual patch.
> But what you see is what happens when you mix const and non-const data
> in the same section.
>
> Look for use of __initdata for const data and replace it with __initconst.
>
> And modpost cannot warn about it as gcc errors out before we look at the
> .o file with modpost.

OIC, thanks. Hmmm... in init.h, I see __{dev|cpu|mem}initconst but no
__initconst. The data structure in question is used from module init
function tagged properly with __init. What should be done here?


--
tejun

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/