From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why no Kconfig in "kernel" subdir?
Date: Fri, 14 Nov 2003 16:34:26 -0500 [thread overview]
Message-ID: <3FB54A62.6020601@nortelnetworks.com> (raw)
In-Reply-To: 20031114092319.5260bd01.rddunlap@osdl.org
Randy.Dunlap wrote:
> I consider PREEMPT and SMP arch-specific, not generic.
Interesting. Might I ask why? I thought that most of PREEMPT was
pretty arch-neutral.
> Will init/Kconfig do what you want?
As long as there is some place to put generic options that are
applicable to the system as a whole, then I'm happy.
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 prev parent reply other threads:[~2003-11-14 21:34 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
2003-11-14 21:34 ` Chris Friesen [this message]
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=3FB54A62.6020601@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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