linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Wen Congyang <wency@cn.fujitsu.com>
Subject: Re: section mismatch for acpi_unmap_lsapic()
Date: Mon, 17 Sep 2012 13:07:29 +0200	[thread overview]
Message-ID: <20120917110729.GA1018@gmail.com> (raw)
In-Reply-To: <20120914163809.GA6854@cantor.us.oracle.com>


* Jerry Snitselaar <dev@snitselaar.org> wrote:

> Commit 13ad20c1 "x86 cpu_hotplug: unmap cpu2node when the cpu is
> hotremoved" in linux-next added code to acpi_unmap_lsapic() that
> causes section mismatch warnings:
> 
> WARNING: vmlinux.o(.text+0x694f2): Section mismatch in reference from the function acpi_unmap_lsapic()
> 	  to the function .cpuinit.text:numa_clear_node()
> WARNING: vmlinux.o(.text+0x694eb): Section mismatch in reference from the function acpi_unmap_lsapic() 
> 	  to the variable .cpuinit.data:__apicid_to_node
> 
> 
> Does acpi_unmap_lsapic() need a wrapper like the one that was made for
> acpi_map_lsapic() or can it just be annotated __ref ? I guess my
> question is would be there be a reason that the wrapper was created
> for acpi_map_lsapic() instead of just annotating __ref besides
> allowing the code for _apic_map_lsapic() to be dropped when
> HOTPLUG_CPU wasn't configured?

That commit comes from -mm AFAICS. Involved parties Cc:-ed.

Thanks,

	Ingo

  reply	other threads:[~2012-09-17 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 16:38 section mismatch for acpi_unmap_lsapic() Jerry Snitselaar
2012-09-17 11:07 ` Ingo Molnar [this message]
2012-09-18  1:40   ` Wen Congyang
2012-09-18 19:50     ` Andrew Morton

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=20120917110729.GA1018@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=wency@cn.fujitsu.com \
    --cc=x86@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).