From: Dirk Behme <dirk.behme@googlemail.com>
To: Felipe Balbi <felipe.lima@indt.org.br>,
linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: Fix section mismatch warnings in omap-rng
Date: Thu, 04 Jan 2007 18:04:22 +0100 [thread overview]
Message-ID: <459D3396.8020604@googlemail.com> (raw)
In-Reply-To: <1168015759.7712.7.camel@balbi>
Felipe Balbi wrote:
> Hello Dirk,
>
>
>>-static int __init omap_rng_probe(struct platform_device *pdev)
>>+static int __devinit omap_rng_probe(struct platform_device *pdev)
>>-static int __exit omap_rng_remove(struct platform_device *pdev)
>>+static int __devexit omap_rng_remove(struct platform_device *pdev)
>
>
> Actually, this will only be true if CONFIG_HOTPLUG is set to "y". This
> way __devinit is defined to "null".
>
> If we set CONFIG_HOTPLUG to "n" the same Section mismatch issue will
> appear.
Ah, yes, I see. Anybody with a better patch for this?
Thanks
Dirk
next prev parent reply other threads:[~2007-01-04 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 15:32 [PATCH] ARM: OMAP: Fix section mismatch warnings in omap-rng Dirk Behme
2007-01-05 16:49 ` Felipe Balbi
2007-01-04 17:04 ` Dirk Behme [this message]
2007-01-04 18:01 ` David Brownell
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=459D3396.8020604@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=felipe.lima@indt.org.br \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox