From: Adrian Bunk <bunk@fs.tum.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
<linux-parport@torque.net>
Cc: linux-kernel@vger.kernel.org, <jbradford@dial.pipex.com>,
"Steven W. Dover" <swdlinunx@earthlink.net>
Subject: [patch] simplify the Config.in for CONFIG_PARPORT_PC_PCMCIA
Date: Mon, 7 Oct 2002 13:42:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.NEB.4.44.0210071208400.8340-100000@mimas.fachschaften.tu-muenchen.de> (raw)
Hi,
the current Config.in code for CONFIG_PARPORT_PC_PCMCIA in both
2.4.20-pre9 and 2.5.40 has the disadvantage that "make xconfig" shows two
entries for this option (it's harmless since at most one of them is
selectable at any time). The patch below fixes this. It does an
semantically equivalent transformation with the positive side effect that
it's now more simple.
--- linux/drivers/parport/Config.in.old 2002-10-07 13:21:26.000000000 +0200
+++ linux/drivers/parport/Config.in 2002-10-07 13:35:31.000000000 +0200
@@ -24,13 +24,7 @@
bool ' Use FIFO/DMA if available (EXPERIMENTAL)' CONFIG_PARPORT_PC_FIFO
bool ' SuperIO chipset support (EXPERIMENTAL)' CONFIG_PARPORT_PC_SUPERIO
fi
- if [ "$CONFIG_HOTPLUG" = "y" -a "$CONFIG_PCMCIA" != "n" ]; then
- if [ "$CONFIG_PARPORT_PC" = "y" ]; then
- dep_tristate ' Support for PCMCIA management for PC-style ports' CONFIG_PARPORT_PC_PCMCIA $CONFIG_PCMCIA
- else
- dep_tristate ' Support for PCMCIA management for PC-style ports' CONFIG_PARPORT_PC_PCMCIA $CONFIG_PARPORT_PC
- fi
- fi
+ dep_tristate ' Support for PCMCIA management for PC-style ports' CONFIG_PARPORT_PC_PCMCIA $CONFIG_HOTPLUG $CONFIG_PCMCIA $CONFIG_PARPORT_PC
fi
if [ "$CONFIG_ARM" = "y" ]; then
dep_tristate ' Archimedes hardware' CONFIG_PARPORT_ARC $CONFIG_PARPORT
Please apply
Adrian
next reply other threads:[~2002-10-07 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 11:42 Adrian Bunk [this message]
2002-10-07 12:04 ` [patch] simplify the Config.in for CONFIG_PARPORT_PC_PCMCIA Adrian Bunk
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=Pine.NEB.4.44.0210071208400.8340-100000@mimas.fachschaften.tu-muenchen.de \
--to=bunk@fs.tum.de \
--cc=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@torque.net \
--cc=marcelo@conectiva.com.br \
--cc=swdlinunx@earthlink.net \
--cc=torvalds@transmeta.com \
/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).