The definition I refered to:
static struct platform_device *devices[] __initdata = {
NULL,
};
To me however it seems to be irrelevant, since meanwhile I managed to
trigger the error multiple ways by changing something else.
I sent the .tmp_map* files of one failed build to Keith.
--Imre
On Wed, 2005-05-11 at 22:47 +0100, ext Russell King wrote:
> On Wed, May 11, 2005 at 12:05:10PM +0300, Imre Deak wrote:
> > I noticed that the error is triggered by an __initdata definition. It is
> > accessed only from an __init function, so that's ok I think. Removing
> > the __initdata attribute gets rid of the error message.
>
> This sounds very vague. Can you show us the code please?
>
> Note that uninitialised variables with an __initdata marking aren't
> legal.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
