From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josh Juran 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 Message-ID: <957AF8FA-7DA1-48A2-A17E-758F6179DFC7@gmail.com> References: <20140120032757.GA761@windriver.com> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-pb0-f50.google.com ([209.85.160.50]:47827 "EHLO mail-pb0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752710AbaATDlQ (ORCPT ); Sun, 19 Jan 2014 22:41:16 -0500 In-Reply-To: <20140120032757.GA761@windriver.com> Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Paul Gortmaker Cc: Geert Uytterhoeven , "linux-kernel@vger.kernel.org" , Linux/m68k 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