From: tony@atomide.com
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: Fix section mismatch warnings
Date: Tue, 4 Jul 2006 00:56:47 -0700 [thread overview]
Message-ID: <20060704075611.GA4962@atomide.com> (raw)
In-Reply-To: <4479AB04.7080501@gmail.com>
* Dirk Behme <dirk.behme@googlemail.com> [060528 06:53]:
>
> Fix warnings
>
> WARNING: drivers/pcmcia/omap_cf.o - Section mismatch:
> reference to .init.text: from .data between '$d' (at offset
> 0x80) and 'omap_cf_ops'
> WARNING: sound/arm/omap/snd-omap-alsa-aic23.o - Section
> mismatch: reference to .init.text: from .data between '$d'
> (at offset 0x68) and 'aic23_hw_constraints_rates'
>
> Signed-off-by: Dirk Behme <dirk.behme_at_gmail.com>
>
> --- ./sound/arm/omap/omap-alsa-aic23.c_orig 2006-05-28 15:34:02.000000000 +0200
> +++ ./sound/arm/omap/omap-alsa-aic23.c 2006-05-28 15:40:52.000000000 +0200
> @@ -271,7 +271,7 @@ int aic23_get_default_samplerate(void)
> return DEFAULT_SAMPLE_RATE;
> }
>
> -static int __init snd_omap_alsa_aic23_probe(struct platform_device *pdev)
> +static int __devinit snd_omap_alsa_aic23_probe(struct platform_device *pdev)
> {
> int ret;
> struct omap_alsa_codec_config *codec_cfg;
> --- ./drivers/pcmcia/omap_cf.c_orig 2006-05-28 15:32:25.000000000 +0200
> +++ ./drivers/pcmcia/omap_cf.c 2006-05-28 15:40:56.000000000 +0200
> @@ -203,7 +203,7 @@ static struct pccard_operations omap_cf_
> * "what chipselect is used". Boards could want more.
> */
>
> -static int __init omap_cf_probe(struct device *dev)
> +static int __devinit omap_cf_probe(struct device *dev)
> {
> unsigned seg;
> struct omap_cf_socket *cf;
>
Pushing today.
Tony
prev parent reply other threads:[~2006-07-04 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 13:52 [PATCH] ARM: OMAP: Fix section mismatch warnings Dirk Behme
2006-07-04 7:56 ` tony [this message]
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=20060704075611.GA4962@atomide.com \
--to=tony@atomide.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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.