Re: const __init

• Next message: Franz Sirl: "Re: const __init"
• Previous message: Alan Cox: "Re: [RFD w/info-PATCH] device arguments from lookup, partion code"
• In reply to: Jeff Garzik: "Re: const __init"
• Next in thread: Jeff Garzik: "Re: const __init"
• Reply: Jeff Garzik: "Re: const __init"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sun, 20 May 2001, Jeff Garzik wrote:
> Geert Uytterhoeven wrote:
> > Since a while include/linux/init.h contains the line
> >
> > * Also note, that this data cannot be "const".
> >
> > Why is this? Because const data will be put in a different section?
>
> Causes a "section type conflict" build error, at least on x86.

On m68k I only saw section type conflict errors when using __init while it
should have been __initdata.

Gr{oetje,eeting}s,

                                                Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
-
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/

• Next message: Franz Sirl: "Re: const __init"
• Previous message: Alan Cox: "Re: [RFD w/info-PATCH] device arguments from lookup, partion code"
• In reply to: Jeff Garzik: "Re: const __init"
• Next in thread: Jeff Garzik: "Re: const __init"
• Reply: Jeff Garzik: "Re: const __init"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed May 23 2001 - 21:00:38 EST