| 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: <9e4733910707221700o16659129ra2daed0833f02cf0@mail.gmail.com> Date: Sun, 22 Jul 2007 20:00:58 -0400 From: "Jon Smirl" <jonsmirl@...il.com> To: "Paul Mundt" <lethal@...ux-sh.org>, "Jan Engelhardt" <jengelh@...putergmbh.de>, "Git Mailing List" <git@...r.kernel.org>, lkml <linux-kernel@...r.kernel.org> Subject: Re: Git tree for old kernels from before the current tree On 7/22/07, Paul Mundt <lethal@...ux-sh.org> wrote: > Anyone still sending 2.4 patches with the intent of them being moved > forward and applied to a current kernel needs to be killfiled. These patches are coming from companies that aren't interested in participating in the GPL process but are being forced into releasing code because of the license. Some of them will go out of their way to make the changes difficult to read. All of the patches I am looking at come from embedded systems, many of these systems are still shipping 2.4 kernels. Most of the patches contain junk, but there are occasional diamonds. One I'm looking at contains code for accessing encryption hardware. The goal is to look at the vendor diffs and see if I can spot anything useful. Spotting something useful can be hard if there are 100,000 lines of noise in the diffs, I'm also trying to spot missing drivers so that we can ask for more code. -- Jon Smirl jonsmirl@...il.com - 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