From: Scott James Remnant <scott@ubuntu.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: generate modules.builtin
Date: Wed, 27 May 2009 23:38:49 +0200 [thread overview]
Message-ID: <1243460329.7913.1.camel@wing-commander> (raw)
In-Reply-To: <ac3eb2510905271426m7ef228aq2c86940ee8a727bb@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On Wed, 2009-05-27 at 23:26 +0200, Kay Sievers wrote:
> On Tue, May 26, 2009 at 17:25, Michal Marek <mmarek@suse.cz> wrote:
> > To make it easier for tools like mkinitrd to detect whether a needed
> > module is missing or whether it is compiled into the kernel, install a
> > modules.builtin file listing all modules built into the kernel. This is
> > done by generating an alternate config file with all tristate =y options
> > set to =Y and reading the makefiles with this config included. The built
> > in modules then appear in obj-Y.
>
> That looks very useful.
>
> We like to have that for modprobe not to throw an error if a "module"
> is already in the kernel, because it is compiled in. Only modules with
> parameters show up in /sys/modules/ and they are already handled fine.
>
Agree, this helps us support both distro kernels with some built-ins and
modular kernels.
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-27 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 15:25 [PATCH] kbuild: generate modules.builtin Michal Marek
2009-05-27 21:26 ` Kay Sievers
2009-05-27 21:38 ` Scott James Remnant [this message]
2009-07-03 14:45 ` Michal Marek
2009-07-15 16:39 ` Scott James Remnant
2009-07-15 16:46 ` Kay Sievers
2009-07-15 18:04 ` Andreas Robinson
2009-07-15 19:08 ` Michal Marek
2009-07-15 20:12 ` Andreas Robinson
2009-07-15 20:16 ` Michal Marek
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=1243460329.7913.1.camel@wing-commander \
--to=scott@ubuntu.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
/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