From: "Neshama Parhoti" <pneshama@gmail.com>
To: "Gilad Ben-Yossef" <gilad@codefidence.com>
Cc: "Adrian Bunk" <bunk@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: section mismatch with a platform driver
Date: Mon, 13 Oct 2008 13:11:51 +0200 [thread overview]
Message-ID: <912ec82a0810130411v3846c0efve4fe59c2b598b60a@mail.gmail.com> (raw)
In-Reply-To: <48F3185F.9070700@codefidence.com>
On Mon, Oct 13, 2008 at 11:43 AM, Gilad Ben-Yossef
<gilad@codefidence.com> wrote:
> Can't be sure without seeing the whole picture, but the most probable
> solution is to drop that __init from the probe function. It's seems wrong as
> in theory the probe function can be called at any time in the life of the
> kernel, not just in this module init, even if in practice this will never
> happen, as I suspect is the case with such a platform driver.
Yes, thanks, removing that macro did make the warning go away.
That's weird because I was using other in-tree drivers as a template for this,
and they don't have this section mismatch problem...
>
> Gilad
>
>
>
> --
> Gilad Ben-Yossef Chief Coffee Drinker
>
> Codefidence Ltd.
> The code is free, your time isn't.(TM)
>
> Web: http://codefidence.com
> Email: gilad@codefidence.com
> Office: +972-8-9316883 ext. 201
> Fax: +972-8-9316885
> Mobile: +972-52-8260388
>
> The Doctor: Don't worry, Reinette, just a nightmare. Everyone
> has nightmares. Even monsters from under the bed have nightmares,
> don't you, monster?
> Reinette: What do monsters have nightmares about?
> The Doctor: Me!
>
next prev parent reply other threads:[~2008-10-13 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 8:19 Neshama Parhoti
2008-10-13 8:51 ` Adrian Bunk
2008-10-13 9:28 ` Neshama Parhoti
2008-10-13 9:43 ` Gilad Ben-Yossef
2008-10-13 11:11 ` Neshama Parhoti [this message]
2008-10-13 9:50 ` Adrian Bunk
2008-10-13 11:13 ` Neshama Parhoti
2008-10-13 16:01 ` Randy Dunlap
2008-10-13 16:29 ` Neshama Parhoti
2008-10-13 16:31 ` Randy Dunlap
2008-10-13 18:58 ` Neshama Parhoti
2008-10-13 19:00 ` Randy Dunlap
2008-10-13 20:22 ` sniper
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=912ec82a0810130411v3846c0efve4fe59c2b598b60a@mail.gmail.com \
--to=pneshama@gmail.com \
--cc=bunk@kernel.org \
--cc=gilad@codefidence.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®