From: "Brian J. Murrell" <cc718ee62b87e84e665d57aa27e6bf39@interlinx.bc.ca>
To: linux-mtd@lists.infradead.org
Subject: MTD Config.in items not escaped by bus availability
Date: Mon, 28 Oct 2002 08:48:32 -0500 [thread overview]
Message-ID: <20021028134832.GQ27880@pc.ilinx> (raw)
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
I have noticed that the whole MTD kernel configuration subsystem
(drivers/mtd/Config.in) in the 2.4.19 kernel is not escaped by any bus
configuration items. That is, even on a kernel that I configure with
no busses (i.e. UML), I am still asked about MTD devices. Should ths
really be so? How can I have any MTD devices with no bus to connect
them to?
If this is the case, can I ask, somebody who knows better than I do,
can you please modify the Config.in for MTD and wrap the whole thing
with a test for the presence of configuration items for the various
different busses that MTD supports? Something like:
mainmenu_option next_comment
comment 'Memory Technology Devices (MTD)'
if [ "$CONFIG_PCMCIA" = "y" -o "$CONFIG_PCMCIA" = "m" -o
"$CONFIG_USB" = "y" -o "$CONFIG_USB" = "m" ]; then
tristate 'Memory Technology Device (MTD) support' CONFIG_MTD
...
fi
endmenu
Thanx,
b.
--
Brian J. Murrell
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-10-30 12:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 13:48 Brian J. Murrell [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 16:22 MTD Config.in items not escaped by bus availability Hicks, Jamey
2002-10-30 17:30 ` Brian J. Murrell
[not found] ` <20021030185507.GA31547@wohnheim.fh-wedel.de>
2002-10-30 19:38 ` Brian J. Murrell
[not found] ` <20021030201608.GA28523@wohnheim.fh-wedel.de>
2002-10-30 20:49 ` Brian J. Murrell
[not found] ` <20021030214341.GC25383@wohnheim.fh-wedel.de>
2002-10-30 22:46 ` Brian J. Murrell
2002-10-31 16:53 ` Jörn Engel
2002-10-31 18:37 ` Jörn Engel
2002-10-31 19:05 ` Brian J. Murrell
2002-10-31 21:00 ` Jörn Engel
2002-11-03 11:59 ` Brian J. Murrell
2002-11-04 14:17 ` Jörn Engel
2002-11-04 14:29 ` Brian J. Murrell
2002-11-04 17:13 ` Jörn Engel
2002-11-06 20:45 ` Brian J. Murrell
2002-11-07 8:00 ` David Woodhouse
2002-11-07 13:50 ` Brian J. Murrell
2002-11-07 14:00 ` David Woodhouse
2002-11-07 15:33 ` Jörn Engel
2002-11-07 15:34 ` David Woodhouse
2002-11-07 15:54 ` Jörn Engel
2002-11-07 15:58 ` David Woodhouse
2002-11-07 16:00 ` Jörn Engel
2002-11-07 15:21 ` Jörn Engel
2002-10-30 22:09 Hicks, Jamey
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=20021028134832.GQ27880@pc.ilinx \
--to=cc718ee62b87e84e665d57aa27e6bf39@interlinx.bc.ca \
--cc=linux-mtd@lists.infradead.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