On Wednesday 27 August 2008, Bartlomiej Zolnierkiewicz wrote: > On Wed, Aug 27, 2008 at 12:06 PM, Bartlomiej Zolnierkiewicz > <bzolnier@xxxxxxxxx> wrote: > > > > Hi, > > > > On Wednesday 27 August 2008, Stephen Rothwell wrote: > >> Hi all, > >> > >> Changes since next-20080826: > > > > it fails to build here with: > > > > arch/x86/kernel/cpu/addon_cpuid_features.c: In function 'detect_extended_topology': > > arch/x86/kernel/cpu/addon_cpuid_features.c:119: error: 'struct cpuinfo_x86' hasno member named 'cpu_core_id' > > arch/x86/kernel/cpu/addon_cpuid_features.c:121: error: 'struct cpuinfo_x86' hasno member named 'phys_proc_id' > > arch/x86/kernel/cpu/addon_cpuid_features.c:130: error: 'struct cpuinfo_x86' hasno member named 'phys_proc_id' > > arch/x86/kernel/cpu/addon_cpuid_features.c:133: error: 'struct cpuinfo_x86' hasno member named 'cpu_core_id' > > make[2]: *** [arch/x86/kernel/cpu/addon_cpuid_features.o] Error 1 > > make[1]: *** [arch/x86/kernel/cpu] Error 2 > > make: *** [arch/x86/kernel] Error 2 > > which is most likely already fixed in x86 tree by > > http://lkml.org/lkml/2008/8/27/34 Confirmed. However now I'm getting device-mapper errors on 'cryptsetup create': dmesg: ... device-mapper: core: bdget failed in dm_suspend device-mapper: ioctl: device doesn't appear to be in the dev hash table. ... cryptsetup: ... Command failed: device-mapper: resume ioctl failed: Invalid argument ... next-20080826 is fine BTW it also seems that certain people need some encouragement to fix the nasty warning first reported by Randy two weeks ago (http://lkml.org/lkml/2008/8/14/207) and later addressed by Rusty (http://lkml.org/lkml/2008/8/16/40) (the solution is said to be fragile but there doesn't seem to be any better one on the horizon so...) -- 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
