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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 24 Oct 2009 21:43:31 +0200 From: Sam Ravnborg <sam@...nborg.org> To: Stefan Richter <stefanr@...6.in-berlin.de> Cc: Theodore Tso <tytso@....edu>, Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>, LKML <linux-kernel@...r.kernel.org>, Nicolas Pitre <nico@...xnic.net>, "Luck, Tony" <tony.luck@...el.com>, Stephen Rothwell <sfr@...b.auug.org.au>, "Luis R. Rodriguez" <mcgrof@...il.com>, Jeff Garzik <jeff@...zik.org>, Robert Richter <robert.richter@....com>, Dmitry Torokhov <dmitry.torokhov@...il.com>, Jean Delvare <khali@...ux-fr.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [RFC] to rebase or not to rebase on linux-next > > We should rely less on linux-next as a cross-compile farm; that's not > its purpose. We can cross-compile ourselves. Hmm, last time I tried to build binutils/gcc I only got: alpha arm sparc64 i386 x86_64 um m68k working. I recall that I managed to build sh and avr32 alas no luck. So please do not expect people that touches code impacting lots of architectures to provide the same level of coverage that -next does. Hay - and sometimes I even fail to buil for all the architectures I have build tool for. Sam -- 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