From: Mike Travis <travis@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <ak@suse.de>,
mingo@elte.hu, Eric Dumazet <dada1@cosmosbay.com>,
Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Fixup NR-CPUS patch for numa
Date: Thu, 17 Jan 2008 10:51:50 -0800 [thread overview]
Message-ID: <478FA3C6.5060401@sgi.com> (raw)
In-Reply-To: <20080117103000.5e97dcd2.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 16 Jan 2008 10:34:39 -0800 travis@sgi.com wrote:
>
>> This patch removes the EXPORT_SYMBOL for:
>>
>> x86_cpu_to_node_map_init
>> x86_cpu_to_node_map_early_ptr
>>
>> ... thus fixing the section mismatch problem.
>
> Which section mismatch problem? Please always quote the error message when
> fixing things like this.
Will do. Basically, it's the error that caused you to add
arch-x86-mm-numa_64c-section-fix.patch
>
>> Also, the mem -> node hash lookup is fixed.
>>
>> Based on 2.6.24-rc6-mm1 + change-NR_CPUS-V3 patchset
>>
>
> hm, I've been hiding from those patches.
>
> Are they ready?
Please wait a moment. I'm resolving the conflicts between what's
in 2.6.24-rc8-mm1 and what's not. I'll resubmit everything shortly.
Thanks!
Mike
WARNING: multiple messages have this Message-ID (diff)
From: Mike Travis <travis@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <ak@suse.de>,
mingo@elte.hu, Eric Dumazet <dada1@cosmosbay.com>,
Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Fixup NR-CPUS patch for numa
Date: Thu, 17 Jan 2008 10:51:50 -0800 [thread overview]
Message-ID: <478FA3C6.5060401@sgi.com> (raw)
In-Reply-To: <20080117103000.5e97dcd2.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 16 Jan 2008 10:34:39 -0800 travis@sgi.com wrote:
>
>> This patch removes the EXPORT_SYMBOL for:
>>
>> x86_cpu_to_node_map_init
>> x86_cpu_to_node_map_early_ptr
>>
>> ... thus fixing the section mismatch problem.
>
> Which section mismatch problem? Please always quote the error message when
> fixing things like this.
Will do. Basically, it's the error that caused you to add
arch-x86-mm-numa_64c-section-fix.patch
>
>> Also, the mem -> node hash lookup is fixed.
>>
>> Based on 2.6.24-rc6-mm1 + change-NR_CPUS-V3 patchset
>>
>
> hm, I've been hiding from those patches.
>
> Are they ready?
Please wait a moment. I'm resolving the conflicts between what's
in 2.6.24-rc8-mm1 and what's not. I'll resubmit everything shortly.
Thanks!
Mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-01-17 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080116183438.506737000@sgi.com>
2008-01-16 18:34 ` [PATCH 1/1] x86: Fixup NR-CPUS patch for numa travis
2008-01-16 18:34 ` travis
2008-01-17 18:30 ` Andrew Morton
2008-01-17 18:30 ` Andrew Morton
2008-01-17 18:51 ` Mike Travis [this message]
2008-01-17 18:51 ` Mike Travis
2008-01-18 12:08 ` Ingo Molnar
2008-01-18 12:08 ` 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=478FA3C6.5060401@sgi.com \
--to=travis@sgi.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.