From: Russell King <rmk+lkml@arm.linux.org.uk>
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: Fri, 13 Aug 2004 13:12:36 +0100 [thread overview]
Message-ID: <20040813131236.B5416@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040813110137.GY13377@fs.tum.de>; from bunk@fs.tum.de on Fri, Aug 13, 2004 at 01:01:37PM +0200
On Fri, Aug 13, 2004 at 01:01:37PM +0200, Adrian Bunk wrote:
> On Fri, Aug 13, 2004 at 12:54:25PM +0200, Roman Zippel wrote:
> > Hi,
> >
> > On Fri, 13 Aug 2004, Evgeniy Polyakov wrote:
> >
> > > On Fri, 2004-08-13 at 14:32, Roman Zippel wrote:
> > > > Hi,
> > > >
> > > > On Fri, 13 Aug 2004, Adrian Bunk wrote:
> > > >
> > > > > config W1
> > > > > tristate "Dallas's 1-wire support"
> > > > > + select NET
> > > >
> > > > What's wrong with a simple dependency?
> > >
> > > W1 requires NET, and thus depends on it.
> > > If you _do_ want W1 then you _do_ need network and then NET must be
> > > selected.
> >
> > A simple "depends on NET" does this as well, I see no reason to abuse
> > select.
>
> In the case of NET the discussion is mostly hypothetically since nearly
> everyone has enabled NET.
In which case, can we remove the user-visibility of CONFIG_NET and
instead make all the protocols automatically select it.
I find the over-use of "select" distasteful, and produces a counter-
intuitive configuration system. I'll carry on complaining each time
I see a patch on LKML which introduces yet another over-use of this
feature without properly considering the consequences of doing so.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-08-13 12:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 10:17 [2.6 patch] let W1 select NET 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 [this message]
2004-08-16 2:18 ` Miles Bader
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=20040813131236.B5416@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bunk@fs.tum.de \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.