From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Patrick Caulfield <pcaulfie@redhat.com>,
Steven Whitehouse <swhiteho@redhat.com>,
teigland@redhat.com, cluster-devel@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.22 regression fix] DLM must depend on SYSFS
Date: Sat, 7 Jul 2007 23:11:10 +0200 [thread overview]
Message-ID: <20070707211110.GL3492@stusta.de> (raw)
In-Reply-To: <alpine.LFD.0.999.0707071350380.31544@woody.linux-foundation.org>
On Sat, Jul 07, 2007 at 01:51:55PM -0700, Linus Torvalds wrote:
>
>
> On Sat, 7 Jul 2007, Adrian Bunk wrote:
> >
> > The dependency of DLM on SYSFS got lost in
> > commit 6ed7257b46709e87d79ac2b6b819b7e0c9184998 resulting in the
> > following compile error with CONFIG_DLM=y, CONFIG_SYSFS=n:
>
> Hmm. Shouldn't we make that a "select", the way we already do for
> CONFIGFS_FS?
"select" is more user friendly while "depends on" makes it easier to
disable options.
Usually I'm for the usage of "select" in such cases, but since this is
with CONFIG_EMBEDDED=y where users can be expected to know better what
they are doing I'd say a "depends on" is fine.
CONFIGFS_FS as a helper for some few file systems is also a different
situation from SYSFS that is a dependency of much more options.
> Linus
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:[~2007-07-07 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 4:14 [2.6.22 regression fix] DLM must depend on SYSFS Adrian Bunk
2007-07-07 20:51 ` Linus Torvalds
2007-07-07 21:11 ` Adrian Bunk [this message]
2007-07-07 21:18 ` Linus Torvalds
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=20070707211110.GL3492@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=pcaulfie@redhat.com \
--cc=swhiteho@redhat.com \
--cc=teigland@redhat.com \
--cc=torvalds@linux-foundation.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