From: Tomas Szepe <szepe@pinerecords.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: alan@lxorguk.ukuu.org.uk, B.Zolnierkiewicz@elka.pw.edu.pl,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [TRIVIAL] kill surplus menu in IDE Kconfig
Date: Sun, 27 Jul 2003 14:39:47 +0200 [thread overview]
Message-ID: <20030727123947.GC24002@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307271425140.717-100000@serv>
> [zippel@linux-m68k.org]
>
> > Patch against -bk3.
>
> Moving up BLK_DEV_HD_ONLY like this is probably not a good idea, it makes
> everything a submenu of this, what might be confusing.
It's logical though. :)
> Try the patch below instead, it fixes the menu structure, everything which
> requires BLK_DEV_IDEDMA_PCI is now also under that menu.
Your patch seems to be against test1 vanilla -- it doesn't apply to -bk3.
> +menuconfig IDE
How exactly does menuconfig work, anyway?
It's not a "block command" -> how will kconf know which entries to put
in the submenu?
What if I have
menuconfig FOO
bool "foo"
menuconfig BAR
bool "bar"
config BAZ
bool "baz"
depends on FOO && BAR
Where is BAZ going to show up and why?
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-07-27 12:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 20:00 [TRIVIAL] kill surplus menu in IDE Kconfig Tomas Szepe
2003-07-27 2:39 ` Randy.Dunlap
2003-07-27 11:01 ` Alan Cox
2003-07-27 11:25 ` Tomas Szepe
2003-07-27 11:28 ` Alan Cox
2003-07-27 11:42 ` Tomas Szepe
2003-07-27 12:29 ` Roman Zippel
2003-07-27 12:39 ` Tomas Szepe [this message]
2003-07-27 13:31 ` Roman Zippel
2003-07-29 17:24 ` Bartlomiej Zolnierkiewicz
2003-07-30 5:57 ` Tomas Szepe
2003-07-30 16:30 ` [PATCH] " Bartlomiej Zolnierkiewicz
2003-07-30 22:27 ` Roman Zippel
2003-07-31 9:03 ` Tomas Szepe
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=20030727123947.GC24002@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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).