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: Thu, 6 Mar 2008 20:39:50 -0800 From: Greg KH <greg@...ah.com> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: linux-next: Tree for March 7 On Fri, Mar 07, 2008 at 02:18:56PM +1100, Stephen Rothwell wrote: > Hi all, > > I have created today's linux-next tree at > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git > (tar balls at > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). > > You can see which trees have been included by looking in the Next/Trees > file in the source. There are also quilt-import.log and merge.log files > in the Next directory. Between each merge, the tree was built with > allmodconfig for both powerpc and x86_64. > > There were a few merge conflicts (trivial) and one build break. I have > notified the appropriate people. > > We are up to 44 trees, more are welcome (even if they are currently > empty). The influx of new trees has been underwhelming. Thanks to those > who have contributed, and to those who haven't, please do. > > Status of my local build tests is at > http://kisskb.ellerman.id.au/kisskb/branch/9/. If maintainers want to > give advice about cross compilers/configs that work, we are always open > to add more builds. Build results from today on also include the actual > compiler version string. > > It looks like this one is going to build fail the same way as yesterday's tree: > > drivers/usb/core/hub.c:633: error: 'struct usb_device' has no member named 'persist_enabled' > drivers/usb/core/hub.c:719: error: 'struct usb_device' has no member named 'reset_resume' > > for any config with CONFIG_PM disabled. I have a patch in my to-apply queue for this, so hopefully it will not happen tomorrow :) thanks, greg k-h -- 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