From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: why no Kconfig in "kernel" subdir?
Date: Fri, 14 Nov 2003 12:05:17 -0500 [thread overview]
Message-ID: <3FB50B4D.1000300@nortelnetworks.com> (raw)
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.
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?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next reply other threads:[~2003-11-14 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 17:05 Chris Friesen [this message]
2003-11-14 17:23 ` why no Kconfig in "kernel" subdir? Randy.Dunlap
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=3FB50B4D.1000300@nortelnetworks.com \
--to=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