From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Joel Becker <jlbec@evilplan.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
James Bottomley <James.Bottomley@suse.de>
Subject: Re: [PATCH] configfs: change depends -> select SYSFS
Date: Sun, 16 Jan 2011 23:19:01 +0000 [thread overview]
Message-ID: <20110116231901.GF22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <AANLkTik=Pv1KdiBa3RbSoqmDC92F33jyFb0b-Ej_iGRN@mail.gmail.com>
On Sun, Jan 16, 2011 at 03:11:57PM -0800, Linus Torvalds wrote:
> Why the hell should a OCFS2 user have to know that he needs to enable
> configfs to be able to enable ocfs2?
>
> The thing is, we should do exactly the reverse of what you say, and
> work towards the goal of "depends on" going away. Right now, the main
> reason to use "depends on" is actually just that our Kconfig solvers
> are stupid, and don't generally handle "select" very well. But that's
> hopefully getting fixed.
How do you eliminate things like "it really depends on having DMA"?
When we configure e.g. s390 or uml kernel, it's not like we could
enable a PCI driver and have architecture magically switch to a
PCI-supporting one, after all...
next prev parent reply other threads:[~2011-01-16 23:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 21:10 [PATCH] configfs: change depends -> select SYSFS Nicholas A. Bellinger
2011-01-16 13:11 ` Stefan Richter
2011-01-16 21:53 ` Nicholas A. Bellinger
2011-01-16 23:06 ` Stefan Richter
2011-01-16 23:11 ` Linus Torvalds
2011-01-16 23:19 ` Al Viro [this message]
2011-01-16 23:45 ` Linus Torvalds
2011-01-17 0:05 ` Al Viro
2011-01-17 7:11 ` Rolf Eike Beer
2011-01-17 0:52 ` Stefan Richter
2011-01-17 1:07 ` Randy Dunlap
2011-01-17 11:16 ` Bernd Petrovitsch
2011-01-16 23:14 ` Nicholas A. Bellinger
2011-01-17 0:22 ` James Bottomley
2011-01-17 6:05 ` Nicholas A. Bellinger
2011-01-17 18:24 ` Randy Dunlap
2011-01-17 22:10 ` Nicholas A. Bellinger
2011-01-18 0:13 ` Randy Dunlap
2011-01-18 0:46 ` Nicholas A. Bellinger
2011-01-17 18:11 ` Randy Dunlap
2011-01-16 17:54 ` Linus Torvalds
2011-01-16 21:44 ` Nicholas A. Bellinger
-- strict thread matches above, loose matches on Subject: below --
2011-01-10 19:45 Nicholas A. Bellinger
2011-01-10 23:46 ` Joel Becker
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=20110116231901.GF22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=James.Bottomley@suse.de \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=randy.dunlap@oracle.com \
--cc=stefanr@s5r6.in-berlin.de \
--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;
as well as URLs for NNTP newsgroup(s).