public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Roman Zippel <zippel@linux-m68k.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: linux kernel conf 0.8
Date: Wed, 09 Oct 2002 16:41:58 -0400	[thread overview]
Message-ID: <3DA49496.10401@pobox.com> (raw)
In-Reply-To: 20021009212613.A12743@mars.ravnborg.org

Sam Ravnborg wrote:
> But there is a good reason why they do it.
> Take a look at dirvers/video/Config.in for example.
> See the size of the big if's. They span several pages if not the whole file.
> Why they do this is simple. Only check for PCI once, and group all
> PCI stuff there.
> With the syntax Roman propose we see instead that _each_ config option
> check for PCI. Which is good IMHO.

That falls apart for multiple-bus drivers.

The way the current config files handle this seems reasonable...  for 
example drivers/net/ in fact _already_ splits things up by bus type to 
some extent.  But this is not a hard and fast rule, just easing some pain.


> But the whole argumentation boils down to something rahter simple:
> 1) Shall we group configuration files together
> 2) Shall we group related files together


This reminds me of another point:

An eventual goal is for people, mostly initial driver merges or vendors, 
to be able to add a simple driver without patching _any_ files.

Which implies that the equivalent of "source drivers/net/Config*" 
(wildcarding) in Roman's system would be useful.  Or maybe "source 
drivers/net" and it knows that when given a directory it should scan for 
all Config* files in that dir.

	Jeff




  reply	other threads:[~2002-10-09 20:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0210081830350.4396-100000@home.transmeta.com>
2002-10-09 12:01 ` linux kernel conf 0.8 Roman Zippel
2002-10-09 13:35   ` Jeff Garzik
2002-10-09 13:55     ` Roman Zippel
2002-10-09 14:07       ` Jeff Garzik
2002-10-09 14:14       ` [kbuild-devel] " Brendan J Simon
2002-10-09 14:28         ` Jeff Garzik
2002-10-09 14:24   ` Brendan J Simon
2002-10-09 14:34     ` Randy.Dunlap
2002-10-09 14:45       ` J.A. Magallon
2002-10-09 15:14         ` Roman Zippel
2002-10-09 15:16       ` Linus Torvalds
2002-10-09 15:19         ` Randy.Dunlap
2002-10-09 16:29           ` Roman Zippel
2002-10-09 16:40             ` Christoph Hellwig
2002-10-09 18:39               ` Roman Zippel
2002-10-09 18:52                 ` Peter Samuelson
2002-10-09 19:28                   ` Randy.Dunlap
2002-10-09 19:39                     ` Sam Ravnborg
2002-10-09 19:47                       ` Randy.Dunlap
2002-10-09 14:55     ` [kbuild-devel] " Roman Zippel
2002-10-09 17:16   ` Sam Ravnborg
2002-10-09 17:37     ` Linus Torvalds
2002-10-09 17:55       ` Sam Ravnborg
2002-10-09 18:47         ` Linus Torvalds
2002-10-09 19:26           ` Sam Ravnborg
2002-10-09 20:41             ` Jeff Garzik [this message]
2002-10-09 22:49               ` Roman Zippel
2002-10-10 14:18                 ` Jeff Garzik
2002-10-10 17:29                   ` Sam Ravnborg
2002-10-10 17:32                     ` Jeff Garzik
2002-10-10 17:51                       ` Sam Ravnborg
2002-10-09 23:49         ` [kbuild-devel] " Brendan J Simon
2002-10-09 18:35       ` Jeff Garzik
2002-10-09  0:40 Roman Zippel

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=3DA49496.10401@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@transmeta.com \
    --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