On Wed, Mar 5, 2014 at 10:58 AM, Dongsheng Yang
wrote:
> Commit 411cf180f introduce function uncore_cpumask_init() and it is only
> called in __init intel_uncore_init(). But it is not marked with __init,
> then the following warning is there when building.
>
I did not get this warning when
Commit 411cf180f introduce function uncore_cpumask_init() and it is only
called in __init intel_uncore_init(). But it is not marked with __init,
then the following warning is there when building.
WARNING: vmlinux.o(.text+0x2464a): Section mismatch in reference from the
function
Commit 411cf180f introduce function uncore_cpumask_init() and it is only
called in __init intel_uncore_init(). But it is not marked with __init,
then the following warning is there when building.
WARNING: vmlinux.o(.text+0x2464a): Section mismatch in reference from the
function
On Wed, Mar 5, 2014 at 10:58 AM, Dongsheng Yang
yangds.f...@cn.fujitsu.com wrote:
Commit 411cf180f introduce function uncore_cpumask_init() and it is only
called in __init intel_uncore_init(). But it is not marked with __init,
then the following warning is there when building.
I did not get
4 matches
Mail list logo