linux-kernel - Re: [PATCH 14/17] ARM: davinci: don't mark da850_register_cpufreq as _

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] [day] [month] [year] [list]

Date:	Thu, 4 Oct 2012 18:48:25 +0530
From:	Sekhar Nori <nsekhar@...com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	<linux-arm-kernel@...radead.org>, <arm@...nel.org>,
	<linux-kernel@...r.kernel.org>, Kevin Hilman <khilman@...com>
Subject: Re: [PATCH 14/17] ARM: davinci: don't mark da850_register_cpufreq
 as __init

On 10/2/2012 10:06 PM, Arnd Bergmann wrote:
> The mityomapl138_cpufreq_init and read_factory_config function in
> board-mityomapl138.c are not __init functions and might be called
> at a later stage, so da850_register_cpufreq must not be __init either.
> 
> Without this patch, building da8xx_omapl_defconfig results in:
> 
> WARNING: arch/arm/mach-davinci/built-in.o(.text+0x2eb4): Section mismatch in reference from the function read_factory_config() to the function .init.text:da850_register_cpufreq()
> The function read_factory_config() references
> the function __init da850_register_cpufreq().
> This is often because read_factory_config lacks a __init
> annotation or the annotation of da850_register_cpufreq is wrong.
> 
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> Cc: Sekhar Nori <nsekhar@...com>
> Cc: Kevin Hilman <khilman@...com>

Acked-by: Sekhar Nori <nsekhar@...com>

Regards,
Sekhar
--
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/