From: Ingo Molnar <mingo@elte.hu>
To: Leonardo Potenza <leo.potenza@gmail.com>
Cc: kernel-janitors@vger.kernel.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86: fix section mismatch warnings in kernel/setup_percpu.c
Date: Sun, 18 Jan 2009 23:59:45 +0100 [thread overview]
Message-ID: <20090118225945.GA3845@elte.hu> (raw)
In-Reply-To: <200901182303.56911.lpotenza@inwind.it>
* Leonardo Potenza <leo.potenza@gmail.com> wrote:
> From: Leonardo Potenza <lpotenza@inwind.it>
>
> The function setup_cpu_local_masks() has been marked __init, in order to remove the following section mismatch messages:
>
> WARNING: vmlinux.o(.text+0x3c2c7): Section mismatch in reference from the function setup_cpu_local_masks() to the function .init.text:alloc_bootmem_cpumask_var()
> The function setup_cpu_local_masks() references
> the function __init alloc_bootmem_cpumask_var().
> This is often because setup_cpu_local_masks lacks a __init
> annotation or the annotation of alloc_bootmem_cpumask_var is wrong.
>
> WARNING: vmlinux.o(.text+0x3c2d3): Section mismatch in reference from the function setup_cpu_local_masks() to the function .init.text:alloc_bootmem_cpumask_var()
> The function setup_cpu_local_masks() references
> the function __init alloc_bootmem_cpumask_var().
> This is often because setup_cpu_local_masks lacks a __init
> annotation or the annotation of alloc_bootmem_cpumask_var is wrong.
>
> WARNING: vmlinux.o(.text+0x3c2df): Section mismatch in reference from the function setup_cpu_local_masks() to the function .init.text:alloc_bootmem_cpumask_var()
> The function setup_cpu_local_masks() references
> the function __init alloc_bootmem_cpumask_var().
> This is often because setup_cpu_local_masks lacks a __init
> annotation or the annotation of alloc_bootmem_cpumask_var is wrong.
>
> WARNING: vmlinux.o(.text+0x3c2eb): Section mismatch in reference from the function setup_cpu_local_masks() to the function .init.text:alloc_bootmem_cpumask_var()
> The function setup_cpu_local_masks() references
> the function __init alloc_bootmem_cpumask_var().
> This is often because setup_cpu_local_masks lacks a __init
> annotation or the annotation of alloc_bootmem_cpumask_var is wrong.
>
> Signed-off-by: Leonardo Potenza <lpotenza@inwind.it>
applied to tip/x86/urgent, thanks Leonardo!
Ingo
prev parent reply other threads:[~2009-01-18 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 22:03 Leonardo Potenza
2009-01-18 22:59 ` Ingo Molnar [this message]
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=20090118225945.GA3845@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=leo.potenza@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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®