[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1082.1195661709@redhat.com>
Date: Wed, 21 Nov 2007 16:15:09 +0000
From: David Howells <dhowells@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: dhowells@...hat.com,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, apw@...dowen.org,
balbir@...ux.vnet.ibm.com
Subject: Re: mm snapshot broken-out-2007-11-20-01-45.tar.gz uploaded
What does broken-out-2007-11-20-01-45.tar.gz apply to? I can't get it to
apply to either Linus's current GIT tree or the 2.6.24-rc3 tree. Both result
in errors.
On the other hand, I have managed to adjust my patches to work with the
2.6.24-rc3-mm1 applied to 2.6.24-rc3. It builds for:
MN10300 defconfig
MN10300 allnoconfig
X86_64 defconfig CONFIG_IA32_AOUT=n
X86_64 defconfig CONFIG_IA32_AOUT=m
X86_64 defconfig CONFIG_IA32_AOUT=y
i386 defconfig CONFIG_BINFMT_AOUT=n
i386 defconfig CONFIG_BINFMT_AOUT=m
i386 defconfig CONFIG_BINFMT_AOUT=y
sparc defconfig
sparc64 defconfig CONFIG_BINFMT_AOUT32=n
sparc64 defconfig CONFIG_BINFMT_AOUT32=y
It almost completely builds for MN10300 allyesconfig and allmodconfig, but for
asm/kvm.h not existing (header checking bug?) and a sample program not
compiling (uses something not provided by most arches).
Most other arches just don't compile to some extent or other for reasons that
aren't to do with my patches, but mostly due to pgtable_t not being defined.
I can even use the MN10300 defconfig kernel:
-bash-3.00# uname -a
Linux asb2303-4 2.6.24-rc3-mm1-g026f9b13 #3 PREEMPT Wed Nov 21 15:02:37 GMT 2007 mn10300 mn10300 mn10300 GNU/Linux
Note, however, I don't expect these modified patches to necessarily work with
Linus's kernel. There seem to be some general changes in -mm that I don't
know whether you'll be sending them upstream or not.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists