lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 4 Jan 2010 15:48:43 -0800 From: Jesse Barnes <jbarnes@...tuousgeek.org> To: Matthew Wilcox <matthew@....cx> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: linux-next: pci tree build failure On Mon, 4 Jan 2010 16:10:01 -0700 Matthew Wilcox <matthew@....cx> wrote: > On Tue, Jan 05, 2010 at 09:55:43AM +1100, Stephen Rothwell wrote: > > Today's linux-next build (powerpc ppc64_defconfig) failed like this: > > > > drivers/pci/hotplug/rpaphp_core.c:433: error: unknown field > > 'get_max_bus_speed' specified in initializer > > drivers/pci/hotplug/rpaphp_core.c:433: warning: excess elements in > > struct initializer drivers/pci/hotplug/rpaphp_core.c:433: warning: > > (near initialization for 'rpaphp_hotplug_slot_ops') > > > > Caused by commit 7227d60c98ad0e1af49c717a62515d74002dd754 ("PCI: > > Make current and maximum bus speeds part of the PCI core"). > > > > I have used the version of the pci tree from next-20100104 for > > today. > > Doh, sorry. I don't have a handy powerpc environment around to test > with. Can you try just deleting line 433? (this should actually be > the correct fix). I just pushed that into my linux-next tree. Thanks, -- Jesse Barnes, Intel Open Source Technology Center -- 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