linux-kernel - Re: [PATCH] staging: ram_console: Fix section mismatches

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:	Thu, 8 Mar 2012 09:56:45 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	John Stultz <john.stultz@...aro.org>, linux-kernel@...r.kernel.org,
	Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH] staging: ram_console: Fix section mismatches

On Thu, Mar 08, 2012 at 01:08:04AM -0800, Stephen Boyd wrote:
> WARNING: vmlinux.o(.text+0x25d5fc): Section mismatch in reference
> from the function ram_console_driver_probe() to the function
> .init.text:ram_console_init()
> The function ram_console_driver_probe() references
> the function __init ram_console_init().
> This is often because ram_console_driver_probe lacks a __init
> annotation or the annotation of ram_console_init is wrong.
> 
> Mark ram_console_driver_probe() as __devinit because it's a probe
> function and propagate the __devinit markings to the __init
> functions the probe calls.

What .config configuration causes this to happen?  I don't see this here
in my builds, what am I doing wrong?

thanks,

greg k-h
--
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/