From: Josh Juran <jjuran@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.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>
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 [thread overview]
Message-ID: <957AF8FA-7DA1-48A2-A17E-758F6179DFC7@gmail.com> (raw)
In-Reply-To: <20140120032757.GA761@windriver.com>
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
next prev parent reply other threads:[~2014-01-20 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 9:40 don't use module_init in non-modular ... (was: Re: [PATCH] m68k: don't use module_init in non-modular mvme16x/rtc.c code) Geert Uytterhoeven
2014-01-20 3:27 ` Paul Gortmaker
2014-01-20 3:41 ` Josh Juran [this message]
2014-01-21 14:36 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=957AF8FA-7DA1-48A2-A17E-758F6179DFC7@gmail.com \
--to=jjuran@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox