From: Tony Lindgren <tony@atomide.com>
To: Jonathan McDowell <noodles@earth.li>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] Fix section mismatch warnings on some OMAP1 boards
Date: Tue, 11 Nov 2008 16:36:38 -0800 [thread overview]
Message-ID: <20081112003637.GU3984@atomide.com> (raw)
In-Reply-To: <20081111225720.GA3162@earth.li>
* Jonathan McDowell <noodles@earth.li> [081111 15:43]:
> I got some section mismatch warnings when compiling latest git for
> MACH_AMS_DELTA this evening; this seems to be due to a missing
> __initdata on the omap_board_config_kernel. Adding it fixes the
> warnings. I noticed that although this had been done for other OMAP1
> boards fsample, innovator and voiceblue were all lacking it too, so I
> fixed them up at the same time.
These cannot be __initdata as they are used by get_config() in
plat-omap/common.c, and omap_get_config() is called in some drivers
that could be modules.
Let's rather just get rid of all the omap_board_config_kernel stuff
and use platform_data instead.
Tony
> Signed-off-by: Jonathan McDowell <noodles@earth.li>
>
> -----
> diff --git a/arch/arm/mach-omap1/board-ams-delta.c b/arch/arm/mach-omap1/board-ams-delta.c
> index 2e61839..682cb91 100644
> --- a/arch/arm/mach-omap1/board-ams-delta.c
> +++ b/arch/arm/mach-omap1/board-ams-delta.c
> @@ -172,7 +172,7 @@ static struct omap_usb_config ams_delta_usb_config __initdata = {
> .pins[0] = 2,
> };
>
> -static struct omap_board_config_kernel ams_delta_config[] = {
> +static struct omap_board_config_kernel ams_delta_config[] __initdata = {
> { OMAP_TAG_LCD, &ams_delta_lcd_config },
> { OMAP_TAG_UART, &ams_delta_uart_config },
> { OMAP_TAG_USB, &ams_delta_usb_config },
> diff --git a/arch/arm/mach-omap1/board-fsample.c b/arch/arm/mach-omap1/board-fsample.c
> index db78946..38f4f18 100644
> --- a/arch/arm/mach-omap1/board-fsample.c
> +++ b/arch/arm/mach-omap1/board-fsample.c
> @@ -216,7 +216,7 @@ static struct omap_lcd_config fsample_lcd_config __initdata = {
> .ctrl_name = "internal",
> };
>
> -static struct omap_board_config_kernel fsample_config[] = {
> +static struct omap_board_config_kernel fsample_config[] __initdata = {
> { OMAP_TAG_UART, &fsample_uart_config },
> { OMAP_TAG_LCD, &fsample_lcd_config },
> };
> diff --git a/arch/arm/mach-omap1/board-innovator.c b/arch/arm/mach-omap1/board-innovator.c
> index 7a97f6b..b86eb95 100644
> --- a/arch/arm/mach-omap1/board-innovator.c
> +++ b/arch/arm/mach-omap1/board-innovator.c
> @@ -408,7 +408,7 @@ static struct omap_uart_config innovator_uart_config __initdata = {
> .enabled_uarts = ((1 << 0) | (1 << 1) | (1 << 2)),
> };
>
> -static struct omap_board_config_kernel innovator_config[] = {
> +static struct omap_board_config_kernel innovator_config[] __initdata = {
> { OMAP_TAG_USB, NULL },
> { OMAP_TAG_LCD, NULL },
> { OMAP_TAG_UART, &innovator_uart_config },
> diff --git a/arch/arm/mach-omap1/board-voiceblue.c b/arch/arm/mach-omap1/board-voiceblue.c
> index 3ab5bbf..93de7e0 100644
> --- a/arch/arm/mach-omap1/board-voiceblue.c
> +++ b/arch/arm/mach-omap1/board-voiceblue.c
> @@ -145,7 +145,7 @@ static struct omap_uart_config voiceblue_uart_config __initdata = {
> .enabled_uarts = ((1 << 0) | (1 << 1) | (1 << 2)),
> };
>
> -static struct omap_board_config_kernel voiceblue_config[] = {
> +static struct omap_board_config_kernel voiceblue_config[] __initdata = {
> { OMAP_TAG_USB, &voiceblue_usb_config },
> { OMAP_TAG_UART, &voiceblue_uart_config },
> };
> -----
>
> J.
>
> --
> jid: noodles@jabber.earth.li
> Are you out of my mind?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-12 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 22:57 [PATCH] Fix section mismatch warnings on some OMAP1 boards Jonathan McDowell
2008-11-12 0:36 ` Tony Lindgren [this message]
2008-11-12 2:00 ` Felipe Balbi
2008-11-12 9:13 ` Jonathan McDowell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081112003637.GU3984@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=noodles@earth.li \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.