lkml.org 
[lkml]   [2014]   [Jan]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: don't use module_init in non-modular ... (was: Re: [PATCH] m68k: don't use module_init in non-modular mvme16x/rtc.c code)
Date
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




\
 
 \ /
  Last update: 2014-01-20 05:01    [W:0.521 / U:0.708 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site