From: "H. Peter Anvin" <hpa@kernel.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Section mismatches in memblock
Date: Tue, 05 Oct 2010 20:04:25 -0700 [thread overview]
Message-ID: <4CABE739.8050001@kernel.org> (raw)
In-Reply-To: <4CABDF3A.2020501@zytor.com>
On 10/05/2010 07:30 PM, H. Peter Anvin wrote:
>
> Wrong functions! Furhtermore, at least the tip tree definitely does not
> have __init_memblock here:
>
Nevermind. I had missed that Ingo had put stuff into core/memblock on
top of x86/memblock, just to be confusing.
-hpa
next prev parent reply other threads:[~2010-10-06 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 22:46 Section mismatches in memblock H. Peter Anvin
2010-10-05 23:30 ` Yinghai Lu
2010-10-06 2:30 ` H. Peter Anvin
2010-10-06 3:04 ` H. Peter Anvin [this message]
2010-10-08 8:16 ` Ingo Molnar
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=4CABE739.8050001@kernel.org \
--to=hpa@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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