| 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: <e84b123e780e21659030c131f4014c36@linuxsystems.it> Date: Thu, 08 May 2014 16:06:43 +0200 From: Niccolò Belli <darkbasic@...uxsystems.it> To: <linux-kernel@...r.kernel.org> Subject: Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf Hi, Sorry for posting on linux-kernel but from my experience nobody ever looks at the kernel bug tracker and I would like to get it fixed before 3.15 gets released. https://bugzilla.kernel.org/show_bug.cgi?id=75671 It's funny to read "Still no boot quirks are called, *so it might not work well on some devices*" in the commit description: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=400362f1d8dcfda3562e80e88cfc2a92cffaf9bf Why does code known to be broken hit the Linus tree? Every new kernel release there is something broken to bisect, it doesn't matter if you wait for the stable release or not. That's frustrating for an end user. Thanks, Niccolò -- 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