| 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
| ||
|
Date: Sun, 19 Jan 2014 19:41:03 -0800 From: Josh Juran <jjuran@...il.com> To: Paul Gortmaker <paul.gortmaker@...driver.com> Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Linux/m68k <linux-m68k@...r.kernel.org> Subject: Re: don't use module_init in non-modular ... (was: Re: [PATCH] m68k: don't use module_init in non-modular mvme16x/rtc.c code) On Jan 19, 2014, at 7:27 PM, Paul Gortmaker wrote: > [Re: don't use module_init in non-modular ... (was: Re: [PATCH] > m68k: don't use module_init in non-modular mvme16x/rtc.c code)] On > 19/01/2014 (Sun 10:40) Geert Uytterhoeven wrote: > >> The word "module" has different meanings: it can be a "loadable >> kernel module", >> or just a "code module". include/linux/init.h seems to agree with >> this: > > I think for most people, "module" means an actual "foo.ko" that can be > fed to insmod. And it is generated by code that is controlled by a > tristate config. Otherwise, sure "init/main.c" is a "code module" and > so is every C file, making the distinction meaningless. Further.... Consider calling the C file a "unit", analogous (and isomorphic) to "translation unit". Josh -- 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