public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org,
	Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
	Roman Zippel <zippel@linux-m68k.org>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: [BK PATCHES] kbuild/kconfig
Date: Wed, 10 Sep 2003 20:34:25 +0100	[thread overview]
Message-ID: <20030910203425.J30046@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030910191411.GA5517@mars.ravnborg.org>; from sam@ravnborg.org on Wed, Sep 10, 2003 at 09:14:11PM +0200

On Wed, Sep 10, 2003 at 09:14:11PM +0200, Sam Ravnborg wrote:
> Hi Linus.
> 
> Here are a few kbuild/kconfig related patches:
> 
> 1) kbuild: Save relevant parts of modules.txt
> 2) kconfig: Allow architectures to select board specific configs
> 3) kbuild: Build minimum in scripts/ when changing configuration
> 4) kbuild: Remove cscope.out during make mrproper 
> 5) kbuild/ppc*: Remove obsolete _config support
> 6) bk ignore scripts/bin2c
> 
> The only patch worth mention is the one allowing architectures
> to select board specific configurations. Adding a few trivial
> changes to conf.c enabled generic support for that.
> ppc* already followed the required setup.
> I did not update arm for this new scheme. Russell?

I'd much rather we keep our current scheme because it makes 100% sense
for ARM since there is no "generic" configuration which covers a subset
of configurations.

To illustrate this fact, here's some statistics on the symbolic usage
between all the default configurations on ARM:

- 414 configuration symbols are only defined on one default configuration
  file.
- 281 configuration symbols occur in between 2 and 9 inclusive files.
- 122 configuration symbols occur between 10 and 46 files.
- 3 configuration symbols occur in all 47 default configuration files.

I'm far from happy doing any conversions to make this work.  The current
system was fine and fit our needs exactly.

-- 
Russell King (rmk@arm.linux.org.uk)	http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
  2.6 ARM Linux   - http://www.arm.linux.org.uk/
  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
  2.6 Serial core

  parent reply	other threads:[~2003-09-10 19:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 19:14 [BK PATCHES] kbuild/kconfig Sam Ravnborg
2003-09-10 19:16 ` kbuild: Save relevant parts of modules.txt Sam Ravnborg
2003-09-10 19:17 ` kconfig: Allow architectures to select board specific configs Sam Ravnborg
2003-09-10 19:17 ` kbuild: Build minimum in scripts/ when changing configuration Sam Ravnborg
2003-09-10 19:58   ` Ricky Beam
2003-09-10 20:13     ` Sam Ravnborg
2003-09-10 21:00       ` Ricky Beam
2003-09-10 19:18 ` kbuild: Remove cscope.out during make mrproper Sam Ravnborg
2003-09-22 17:24   ` GOTO Masanori
2003-09-22 20:55     ` Sam Ravnborg
2003-09-10 19:18 ` kbuild/ppc*: Remove obsolete _config support Sam Ravnborg
2003-09-10 19:34 ` Russell King [this message]
2003-09-10 19:48   ` [BK PATCHES] kbuild/kconfig Sam Ravnborg
2003-09-10 22:13     ` Russell King

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=20030910203425.J30046@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=torvalds@osdl.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