public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why no Kconfig in "kernel" subdir?
Date: Fri, 14 Nov 2003 09:23:19 -0800	[thread overview]
Message-ID: <20031114092319.5260bd01.rddunlap@osdl.org> (raw)
In-Reply-To: <3FB50B4D.1000300@nortelnetworks.com>

On Fri, 14 Nov 2003 12:05:17 -0500 Chris Friesen <cfriesen@nortelnetworks.com> wrote:

| I was adding a new general syscall the other day, and it struck me as 
| odd that there is no Kconfig in the "kernel" subdirectory.
| 
| A quick search shows 36 separate config options being used in that 
| subdirectory (stuff like PREEMPT, SMP, FUTEX, HOTPLUG, SYSCTL, etc). 
| Why is there no Kconfig for it?  As it stands, all of these have to be 
| copied and pasted in every single arch.  This seems odd.

In several cases I expect that you are correct.
In some cases, general config options are now going into init/Kconfig.

| Would people be open to a series of patches that create a new Kconfig 
| and start moving generic stuff to it?  Or are these things really 
| arch-specific enough to warrent massive duplication?

I consider PREEMPT and SMP arch-specific, not generic.

Will init/Kconfig do what you want?

--
~Randy
MOTD:  Always include version info.

  reply	other threads:[~2003-11-14 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 17:05 why no Kconfig in "kernel" subdir? Chris Friesen
2003-11-14 17:23 ` Randy.Dunlap [this message]
2003-11-14 21:34   ` Chris Friesen
2003-11-14 22:07     ` Randy.Dunlap

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=20031114092319.5260bd01.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.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