From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Adrian Bunk <bunk@stusta.de>,
Alexey Dobriyan <adobriyan@gmail.com>,
David Howells <dhowells@redhat.com>, Jens Axboe <axboe@suse.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer
Date: Thu, 24 Aug 2006 11:01:02 -0700 [thread overview]
Message-ID: <20060824110102.d47a8659.rdunlap@xenotime.net> (raw)
In-Reply-To: <1156441724.3012.183.camel@pmac.infradead.org>
On Thu, 24 Aug 2006 18:48:44 +0100 David Woodhouse wrote:
> On Thu, 2006-08-24 at 10:34 -0700, Randy.Dunlap wrote:
> > How do you do that if you have all of ISDN disabled and want/need
> > to enable one ISDN driver? or same problem for V4L(2)/dvb?
> > or several other subsystems? (e.g. sound)
>
> If you _ever_ catch me getting confused because I'm trying to build an
> ISDN driver and I can't work out that in order to do this, I might need
> to first enable CONFIG_ISDN, then I promise you I will change my name by
> deed poll to 'Aunt Tillie'.
I'd rather use menuconfig or xconfig for that instead of editing
.config and reading multiple Kconfig files.
But I'd still prefer to have an "Enable all of this subsystem options first"
switch like I suggested a few months ago. Makes it easier to view
and disable options.
> It isn't hard to find dependencies by looking in the Kconfig files, even
> if they are slightly less blindingly obvious than that example. I think
> 'make xconfig' will even show you the dependencies these days. I
> remember even in about 1996 the Nemesis folks had hacked the old tcl
> xconfig script to show dependencies.
menuconfig or xconfig will show dependencies now.
> Finding the brain-damaged 'select' which is preventing me from turning a
> given option _off_, however, is something I tend to find far more
> difficult. The CONFIG_EMBEDDED crap took up a painful amount of my time
> last week when it bit me too.
Ack.
---
~Randy
next prev parent reply other threads:[~2006-08-24 17:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 13:00 David Howells
2006-08-24 13:13 ` David Woodhouse
2006-08-24 13:34 ` David Howells
2006-08-24 13:40 ` David Woodhouse
2006-08-24 13:54 ` David Howells
2006-08-24 13:47 ` Christoph Hellwig
2006-08-24 14:42 ` Nick Piggin
2006-08-24 15:29 ` Adrian Bunk
2006-08-24 15:44 ` David Woodhouse
2006-08-24 15:58 ` Adrian Bunk
2006-08-24 16:00 ` David Woodhouse
2006-08-24 16:09 ` Adrian Bunk
2006-08-24 16:47 ` Alexey Dobriyan
2006-08-24 17:07 ` Adrian Bunk
2006-08-24 17:16 ` David Woodhouse
2006-08-24 17:34 ` Randy.Dunlap
2006-08-24 17:48 ` David Woodhouse
2006-08-24 17:59 ` Sam Ravnborg
2006-08-25 6:23 ` Jan Engelhardt
2006-08-25 7:19 ` Sam Ravnborg
2006-08-24 18:01 ` Randy.Dunlap [this message]
2006-08-25 6:21 ` Jan Engelhardt
2006-08-25 6:07 ` Jan Engelhardt
2006-08-25 10:37 ` Adrian Bunk
2006-08-25 13:09 ` Alexey Dobriyan
2006-08-24 16:39 ` Jan Engelhardt
2006-08-24 16:44 ` David Woodhouse
2006-08-24 16:48 ` Adrian Bunk
2006-08-24 21:31 ` Johannes Stezenbach
2006-08-25 6:04 ` Jan Engelhardt
2006-08-24 18:39 ` Matthias Schniedermeyer
2006-08-25 6:06 ` Jan Engelhardt
2006-08-24 17:18 ` David Howells
2006-08-24 17:23 ` Adrian Bunk
2006-08-24 16:23 ` Stefan Richter
2006-08-25 12:16 ` Jens Axboe
2006-08-25 13:40 ` David Howells
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=20060824110102.d47a8659.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=adobriyan@gmail.com \
--cc=axboe@suse.de \
--cc=bunk@stusta.de \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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®