In-Reply-To: <20140120032757.GA761@windriver.com>
References: <CAMuHMdWx9QVn1j2QauMQfza_e_+4DHRg9WpZkocCr7+jtjwtMQ@mail.gmail.com> <20140120032757.GA761@windriver.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <957AF8FA-7DA1-48A2-A17E-758F6179DFC7@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Linux/m68k <linux-m68k@vger.kernel.org>
Content-Transfer-Encoding: 7bit
From: Josh Juran <jjuran@gmail.com>
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)
Date: Sun, 19 Jan 2014 19:41:03 -0800
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Sender: linux-kernel-owner@vger.kernel.org

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/