On Thu, 15 Nov 2007, Andrew Morton wrote: > Unfortunately some loon has gone and merged the i386 and x86_64 Kconfig > files. I was fixing that up but I worry what effects these Kconfig changes > might have on, for example, i386 NUMA setups. > > So I'll duck this version, sorry. Is there a tree that I can rediff the patch against? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Andrew Morton <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- References:
- x86_64: Make sparsemem/vmemmap the default memory model
- From: Christoph Lameter <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Andi Kleen <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Christoph Lameter <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Andi Kleen <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Christoph Lameter <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Andrew Morton <[email protected]>
- x86_64: Make sparsemem/vmemmap the default memory model
- Prev by Date: Re: [patch 2/4] Add ARCH_SUPPORTS_OPROFILE
- Next by Date: Re: MIPS RT debug support
- Previous by thread: Re: x86_64: Make sparsemem/vmemmap the default memory model
- Next by thread: Re: x86_64: Make sparsemem/vmemmap the default memory model
- Index(es):
 |