linux-kernel - Re: section mismatch with a platform driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Oct 2008 13:11:51 +0200
From:	"Neshama Parhoti" <pneshama@...il.com>
To:	"Gilad Ben-Yossef" <gilad@...efidence.com>
Cc:	"Adrian Bunk" <bunk@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: section mismatch with a platform driver

On Mon, Oct 13, 2008 at 11:43 AM, Gilad Ben-Yossef
<gilad@...efidence.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@...efidence.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!
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/