| 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: <523FA9A6.40600@web.de> Date: Mon, 23 Sep 2013 04:38:30 +0200 From: Markus Elfring <Markus.Elfring@....de> To: linux-kernel@...r.kernel.org Subject: Re: Would an "information module" be useful? > In the systemd case we have to ensure that we never ever merge a module named "systemd". Interesting ... > We have all kinds of strange modules/drivers. Usually you don't have to think > whether your module is a "ordinary" driver or not... Would it become useful to move "drivers" which do not manage hardware to a separate directory? Should such source files belong to a different software category (or "class")? Regards, Markus -- 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