From: Miles Bader <miles@lsi.nec.co.jp>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let W1 select NET
Date: Mon, 16 Aug 2004 11:18:44 +0900 [thread overview]
Message-ID: <buozn4vvn97.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20040813131236.B5416@flint.arm.linux.org.uk> (Russell King's message of "Fri, 13 Aug 2004 13:12:36 +0100")
Russell King <rmk+lkml@arm.linux.org.uk> writes:
> In which case, can we remove the user-visibility of CONFIG_NET and
> instead make all the protocols automatically select it.
That would kind of annoying for cases where one really does want to
disable it though. A very nice property of the current system is that
when one disables something like _NET, it removes a vast swath of other
options (which removes a lot of clutter from the interface), and _know_
you won't inadvertently drag in _NET by enabling something.
Conversely, the requirement that _NET be enabled to select various
network-related things isn't a problem from a user-interface point of
view, as it's `obvious' that one needs a network to use them (and the
config option to turn networking on is pretty starkly obvious when all
other networking options are removed).
This latter point in particular doesn't hold for some other
relationships (e.g. I seem to recall that various feature require SCSI
somewhat counter-intuitively, as they're not inherently related to it,
but rather have an implementation dependency on the kernel SCSI
infrastructure).
-Miles
--
Somebody has to do something, and it's just incredibly pathetic that it
has to be us. -- Jerry Garcia
next prev parent reply other threads:[~2004-08-16 2:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 10:17 Adrian Bunk
2004-08-13 10:31 ` Evgeniy Polyakov
2004-08-13 10:32 ` Roman Zippel
2004-08-13 10:46 ` Evgeniy Polyakov
2004-08-13 10:54 ` Roman Zippel
2004-08-13 11:01 ` Adrian Bunk
2004-08-13 11:26 ` Bernd Eckenfels
2004-08-13 12:11 ` Roman Zippel
2004-08-13 12:24 ` Adrian Bunk
2004-08-13 17:00 ` Randy.Dunlap
2004-08-15 17:13 ` Roman Zippel
2004-08-13 12:12 ` Russell King
2004-08-16 2:18 ` Miles Bader [this message]
2004-08-13 11:06 ` Evgeniy Polyakov
2004-08-13 10:54 ` Adrian Bunk
2004-08-13 11:06 ` Roman Zippel
2004-08-13 13:52 ` Cornelia Huck
2004-08-13 15:10 ` Evgeniy Polyakov
2004-08-13 15:45 ` Cornelia Huck
2004-08-13 17:12 ` Evgeniy Polyakov
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=buozn4vvn97.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=bunk@fs.tum.de \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.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
all inboxes | Powered by JetHome®