| 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, 27 Feb 2014 17:29:10 -0800 From: Josh Triplett <josh@...htriplett.org> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: linux-next: build failure after merge of the final tree (akpm-current tree related) On Thu, Feb 27, 2014 at 01:40:57PM +1100, Stephen Rothwell wrote: > Hi Josh, > > On Wed, 26 Feb 2014 18:21:29 -0800 Josh Triplett <josh@...htriplett.org> wrote: > > > > On Thu, Feb 27, 2014 at 10:00:26AM +1100, Stephen Rothwell wrote: > > > Please check the build results overnight tonight (for next-20140227 at > > > http://kisskb.ellerman.id.au/linux-next) and submit any more fixes for > > > the allnoconfig build errors. > > > > Checking that site, I don't see any other instances of failures caused > > by allnoconfig. If I'm missing some, could you please point me to the > > page on that site I'm missing? > > That is because your patch was reverted in yesterday's (next-20140226) > linux-next. You will need to look tomorrow (next-20140227) sometime. It looks like the next-20140227 builds have shown up, and I only see one additional allnoconfig build failure exposed by my patch (TTY dependency on cris arch-v10). I sent a patch for that one. I *think* that should have it covered; let me know if you see any other failures. - Josh Triplett -- 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