| 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
| ||
|
Message-ID: <20120225234804.5461de60@schatten.dmk.lab> Date: Sat, 25 Feb 2012 23:48:04 +0100 From: Florian Mickler <florian@...kler.org> To: "werner" <w.landgraf@...ru> Cc: David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org, maciej.rutecki@...il.com Subject: Re: [Bug #42669] 3.3-rc1: compiling problems nvme , l2cap_sock , mc13892-regulator , and snd-pcsp don't work On Fri, 24 Feb 2012 17:55:07 -0400 "werner" <w.landgraf@...ru> wrote: > > > > >> This things happens, because people, after changes, nor > >>compile them > >> subroutines ... :( Much less, test them ... > > > > > In -rc1 were compilation errors in several subroutines, > and almost none of them was fixed until -rc4 . > > And: that's a steady problem (although I bacame tired ond > report only exceptionally about this). > > Generally, people, after patching something, at least > should try to compile the subroutine !!!!!!!!!!!!!! And as David just told you, it compiles fine for him without the fix. Should every developer test every available toolchain combination? > > > W.Landgraf > --- > Professional hosting for everyone - http://www.host.ru -- 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