| 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: <43e72e890911201253obc466c8k2102e04457c48c92@mail.gmail.com> Date: Fri, 20 Nov 2009 12:53:51 -0800 From: "Luis R. Rodriguez" <mcgrof@...il.com> To: linux-kernel@...r.kernel.org Cc: linux-wireless <linux-wireless@...r.kernel.org>, netdev@...r.kernel.org Subject: Re: A generic kernel compatibilty code On Fri, Nov 20, 2009 at 12:51 PM, Luis R. Rodriguez <mcgrof@...il.com> wrote: > On Fri, Nov 20, 2009 at 12:45 PM, Luis R. Rodriguez <mcgrof@...il.com> wrote: >> Everyone and their mother reinvents the wheel when it comes to >> backporting kernel modules. It a painful job and it seems to me an >> alternative is possible. If we can write generic compatibilty code for >> a new routine introduced on the next kernel how about just merging it >> to the kernel under some generic compat module. This would be >> completey ignored by everyone using the stable kernel but can be >> copied by anyone doing backport work. >> >> So I'm thinking something as simple as a generic compat/comat.ko with >> compat-2.6.32.[ch] files. > > FWIW, I meant a compat-2.6.32.[ch] and compat-2.6.31.[ch] and so on. > All these would link to the compat.ko I supose this could juse be a separate tree with some generic compat.ko module. That might work better. Luis -- 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