From: Giacomo Catenazzi <cate@debian.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: andersen@codepoet.org, Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux kernel config converter
Date: Thu, 21 Feb 2002 15:06:59 +0100 [thread overview]
Message-ID: <3C74FF03.8070502@debian.org> (raw)
In-Reply-To: <fa.fsgrt4v.1bngh9t@ifi.uio.no> <fa.hp69onv.i7qtq3@ifi.uio.no>
Jeff Garzik wrote:
> Erik Andersen wrote:
>
>>I like this. It's simple, its clean, and it keeps all the
>>information in one spot. I think we can go a bit farther here
>>and add in a list of the .c files that enabling this feature
>>should add to the Makefile (per the current
>> obj-$(CONFIG_FOO) += foo.o
>>stuff in the current Makefile).
>
> Seriously, yep, that's exactly where we eventually want to be: all
> config, makefile, and help text info in one place. To add a new net
> driver, I want to be able to simply add two files, driver.c and
> driver.conf, and be done with it.
with kbuild-2.5 this can be done easy. We should maintain
the syntax of kbuild-2.5 (or a subset).
But the makefile/makefile.in will remain: not all code
in kernel is drivers, and for the non drivers makefile/config.in
IMHO it is better to have 'central' (per directory/per type)
config and makefile files.
giacomo
next parent reply other threads:[~2002-02-21 14:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fsgrt4v.1bngh9t@ifi.uio.no>
[not found] ` <fa.hp69onv.i7qtq3@ifi.uio.no>
2002-02-21 14:06 ` Giacomo Catenazzi [this message]
2002-02-21 14:26 ` linux kernel config converter Jeff Garzik
2002-02-21 14:39 ` Giacomo Catenazzi
2002-02-21 15:11 ` Jeff Garzik
2002-02-21 16:00 ` Randy.Dunlap
[not found] ` <fa.lqt3hav.190o1i9@ifi.uio.no>
2002-02-21 14:50 ` Giacomo Catenazzi
2002-02-21 14:56 ` David Lang
2002-02-21 15:05 ` Giacomo Catenazzi
[not found] <fa.gq2s5iv.1s4in@ifi.uio.no>
2002-02-21 13:28 ` Giacomo Catenazzi
2002-02-21 14:11 ` Roman Zippel
2002-02-21 14:32 ` Giacomo Catenazzi
2002-02-21 15:19 ` Roman Zippel
2002-02-21 10:48 Roman Zippel
2002-02-21 11:40 ` Jeff Garzik
2002-02-21 12:21 ` Roman Zippel
2002-02-21 12:32 ` Jeff Garzik
2002-02-21 12:54 ` Erik Andersen
2002-02-21 13:21 ` Jeff Garzik
2002-02-21 14:28 ` David Lang
2002-02-21 14:36 ` Jeff Garzik
2002-02-21 14:40 ` David Lang
2002-02-21 15:05 ` Jeff Garzik
2002-02-21 15:41 ` Jason Lunz
2002-02-21 15:54 ` Jeff Garzik
2002-02-21 15:18 ` Alan Cox
2002-02-21 15:08 ` Jeff Garzik
2002-02-21 15:22 ` Gerd Knorr
2002-02-21 15:33 ` Roman Zippel
2002-02-21 18:53 ` Andreas Dilger
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=3C74FF03.8070502@debian.org \
--to=cate@debian.org \
--cc=andersen@codepoet.org \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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