From: Adrian Bunk <bunk@stusta.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH 2.6.19-rc5-mm2] fs/dlm: fix recursive dependency in Kconfig
Date: Tue, 21 Nov 2006 01:12:33 +0100 [thread overview]
Message-ID: <20061121001233.GC5200@stusta.de> (raw)
In-Reply-To: <20061120153528.5ace6089.randy.dunlap@oracle.com>
On Mon, Nov 20, 2006 at 03:35:28PM -0800, Randy Dunlap wrote:
> On Mon, 20 Nov 2006 18:45:09 +0100 Adrian Bunk wrote:
>
> > On Mon, Nov 20, 2006 at 12:45:11PM +0100, Stefan Richter wrote:
> > >...
> > > Anyway. Whatever you chose to do (or already have chosen to do) in
> > > fs/dlm/Kconfig, keep in mind that the "select" keyword is presently only
> > > poorly supported by the various .config generators and that it forces UI
> > > considerations into the Kconfig files which should better not be
> > > overloaded with UI issues. Or in other words: It is rather easy to write
> > > correct and well-supported Kconfig files if you stick with "depend on",
> > > but you get into trouble fast with generous usage of "select".
> >
> > For variables like NET or INET it doesn't matter in practice whether you
> > use "select" or "depends on". But for other variables it makes it really
> > hard for users to enable an option if you use "depends on".
>
> Doing a "select" NET or INET enables a ton of code, which IMO
> should be done explicitly, not covertly by a select.
It seems you misunderstood my statement.
Let me try to phrase it differently:
A "depends on INET" is no problem for users since virtually everyone has
INET enabled.
But a "depends on IP_SCTP" or a "depends on I2C_ALGOBIT" is a
dependency that might create serious problems for users.
> ~Randy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
Patrick Caulfield <pcaulfie@redhat.com>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org,
David Teigland <teigland@redhat.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2.6.19-rc5-mm2] fs/dlm: fix recursive dependency in Kconfig
Date: Tue, 21 Nov 2006 01:12:33 +0100 [thread overview]
Message-ID: <20061121001233.GC5200@stusta.de> (raw)
In-Reply-To: <20061120153528.5ace6089.randy.dunlap@oracle.com>
On Mon, Nov 20, 2006 at 03:35:28PM -0800, Randy Dunlap wrote:
> On Mon, 20 Nov 2006 18:45:09 +0100 Adrian Bunk wrote:
>
> > On Mon, Nov 20, 2006 at 12:45:11PM +0100, Stefan Richter wrote:
> > >...
> > > Anyway. Whatever you chose to do (or already have chosen to do) in
> > > fs/dlm/Kconfig, keep in mind that the "select" keyword is presently only
> > > poorly supported by the various .config generators and that it forces UI
> > > considerations into the Kconfig files which should better not be
> > > overloaded with UI issues. Or in other words: It is rather easy to write
> > > correct and well-supported Kconfig files if you stick with "depend on",
> > > but you get into trouble fast with generous usage of "select".
> >
> > For variables like NET or INET it doesn't matter in practice whether you
> > use "select" or "depends on". But for other variables it makes it really
> > hard for users to enable an option if you use "depends on".
>
> Doing a "select" NET or INET enables a ton of code, which IMO
> should be done explicitly, not covertly by a select.
It seems you misunderstood my statement.
Let me try to phrase it differently:
A "depends on INET" is no problem for users since virtually everyone has
INET enabled.
But a "depends on IP_SCTP" or a "depends on I2C_ALGOBIT" is a
dependency that might create serious problems for users.
> ~Randy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-11-21 0:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 15:52 [Cluster-devel] [PATCH 2.6.19-rc5-mm2] fs/dlm: fix recursive dependency in Kconfig Stefan Richter
2006-11-18 15:52 ` Stefan Richter
2006-11-20 9:48 ` [Cluster-devel] " Patrick Caulfield
2006-11-20 9:48 ` Patrick Caulfield
2006-11-20 11:45 ` [Cluster-devel] " Stefan Richter
2006-11-20 11:45 ` Stefan Richter
2006-11-20 17:45 ` [Cluster-devel] " Adrian Bunk
2006-11-20 17:45 ` Adrian Bunk
2006-11-20 23:35 ` [Cluster-devel] " Randy Dunlap
2006-11-20 23:35 ` Randy Dunlap
2006-11-21 0:12 ` Adrian Bunk [this message]
2006-11-21 0:12 ` Adrian Bunk
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=20061121001233.GC5200@stusta.de \
--to=bunk@stusta.de \
/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.