At Wed, 30 Jul 2008 17:06:35 +1000, Stephen Rothwell wrote: > > Hi all, > > The summary of the difference between 2.6.27-rc1 and today's tree is: > > 1383 files changed, 50871 insertions(+), 37618 deletions(-) > > thanks partly to the include/asm-sh -> arch/sh/include/asm rename, 1307 > kvm commits and 188 xfs commits. > > Changes since next-20080729: > > Temporarily dropped trees: acpi (it is being moved to a new tree and is > just accumulating conflicts against Linus' tree). > v4l-dvb (got lots of conflicts against the version that was > merged to Linus). > > Linus' tree gained a three build fix (from the pci-current tree). > > The driver-core tree had a commit reverted but the problem is actually > elsewhere. > > The battery tree lost its conflicts. > > I have also applied the following patches for known problems: > > hfcmulti is not supported on big endian > cpumask: statement expressions confuse some versions of gcc > tests: lkdtm needs ide.h > > The sparc(32) defconfig build still fails - this is probably a toolchain > problem. I got a build error on ia64 regarding kvm: CC [M] arch/ia64/kvm/../../../virt/kvm/ioapic.o arch/ia64/kvm/../../../virt/kvm/ioapic.c:42:17: error: irq.h: No such file or directory arch/ia64/kvm/../../../virt/kvm/ioapic.c: In function '__kvm_ioapic_update_eoi': arch/ia64/kvm/../../../virt/kvm/ioapic.c:296: error: implicit declaration of function 'kvm_notify_acked_irq' arch/ia64/kvm/../../../virt/kvm/ioapic.c: In function 'ioapic_mmio_write': arch/ia64/kvm/../../../virt/kvm/ioapic.c:389: error: too few arguments to function 'kvm_ioapic_update_eoi' make[1]: *** [arch/ia64/kvm/../../../virt/kvm/ioapic.o] Error 1 Since the build with next-0729 was OK, the culprit looks like the commit: commit 4233cf141eeb8d6363e0fb78e2e2ea391c269200 Author: Marcelo Tosatti <mtosatti@xxxxxxxxxx> Date: Sat Jul 26 17:01:00 2008 -0300 KVM: irq ack notification Takashi -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html