| 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: Wed, 27 Feb 2008 00:36:13 +0100 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Stephen Rothwell <sfr@...b.auug.org.au> CC: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: -next build logs Stephen Rothwell wrote: > On Tue, 26 Feb 2008 19:15:37 +0100 Stefan Richter <stefanr@...6.in-berlin.de> wrote: >> the allmodconfig builds at http://kisskb.ellerman.id.au/kisskb/branch/9/ >> seem to lack a few drivers even though they are properly enabled in the >> respective config. Is it simply because everything is rebuilt on top of >> a previous build? > > That's interesting. I thought they were built from a clean tree each > time but I will discuss this with Michael Ellerman who created this build > system. I noticed it while looking how well drivers/firewire/ (CONFIG_FIREWIRE*) and drivers/ieee1394/ (CONFIG_IEEE1394*) are compiled in -next; i.e. you can just check for the firewire ones as one example of potentially missing compiles. On the other hand, I also saw some LDs without corresponding preceding CCs, so it rather looks like there was already something compiled. >> Do you mail only errors to maintainers or also compiler warnings? > > Currently I am only concerned with actual failures. OK, I will just look myself into the logs then. Thanks, -- Stefan Richter -=====-==--- --=- ==-== http://arcgraph.de/sr/ -- 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