From: Steven Rostedt <rostedt@goodmis.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: akpm@linux-foundation.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, JBeulich@novell.com,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Feedback on "kbuild: generate modules.builtin"
Date: Sun, 20 Sep 2009 10:40:52 -0400 [thread overview]
Message-ID: <1253457652.20020.630.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20090920132856.GA26845@merkur.ravnborg.org>
On Sun, 2009-09-20 at 15:28 +0200, Sam Ravnborg wrote:
> On Fri, Sep 18, 2009 at 12:49:29PM -0700, akpm@linux-foundation.org wrote:
> > From: Michal Marek <mmarek@suse.cz>
> >
> > 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.
>
> Hi Michael.
>
> [Added Steven on cc: as he had done some kconfig
> hacking lately].
Thanks!
>
> Got some time (finally) to look at this.
Unfortunately, I'm about to leave for two weeks. I got LinuxCon and
LinuxPlumbers to present at in Portland, then I fly off to Dresden
Germany to present at OSADL conference there. So I wont have anytime to
look at this until I'm done with these.
But please, keep me posted on any changes like this.
Thanks,
-- Steve
> I understand the functionality and I have myself had the need
> to see builtin modules.
>
> As for the implmentation I have a few comments.
next prev parent reply other threads:[~2009-09-20 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909181949.n8IJnT4R019097@imap1.linux-foundation.org>
2009-09-20 13:28 ` Sam Ravnborg
2009-09-20 14:40 ` Steven Rostedt [this message]
2009-09-20 18:35 ` Sam Ravnborg
2009-09-25 11:04 ` 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=1253457652.20020.630.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.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
all inboxes | Powered by JetHome®