From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: <sam@ravnborg.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [RFC] kbuild: Documentation - how to build external modules
Date: Wed, 21 Apr 2004 12:44:12 +0200 [thread overview]
Message-ID: <50BF37ECE4954A4BA18C08D0C2CF88CB227297@exmail1.se.axis.com> (raw)
> -----Original Message-----
> From: sam@ravnborg.org [mailto:sam@ravnborg.org]
> Sent: 21 April 2004 12:40
> To: Peter Kjellerstedt
> Cc: Sam Ravnborg; linux-kernel@vger.kernel.org
> Subject: Re: [RFC] kbuild: Documentation - how to build
> external modules
>
> >What about external modules that need to be configured
> >using make config & co? Is that possible with this system?
>
> No, this is not possible for now.
> I have thought about a few ways of doing this.
> What I plan to look at is something where the local Kconfig
> file is read along with the .config for the kernel.
> The user will then anly be allowed to tweak config symbols
> defined for the external module, the kernel paramerets are not
> visible, and cannot be modified.
This sounds like what I was looking for.
> But this requires some kconfig tweaking, and first priority is
> to get the basic funtionality working so all (most) people
> are happy with it.
Well, we are still using 2.4, so it is no problem for us yet.
Better get the basics working first. :)
> If anyone has better ideas for handling Kconfig files for external
> modules please tell so.
>
> Sam
//Peter
next reply other threads:[~2004-04-21 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 10:44 Peter Kjellerstedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-21 10:39 sam
2004-04-21 6:22 Peter Kjellerstedt
2004-04-20 21:51 Sam Ravnborg
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=50BF37ECE4954A4BA18C08D0C2CF88CB227297@exmail1.se.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=linux-kernel@vger.kernel.org \
--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®