From: "Philip A. Prindeville" <philipp@redfish-solutions.com>
To: John Linville <linville@tuxdriver.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Pavel Roskin <proski@gnu.org>
Subject: [PATCH] Don't build PCMCIA modules when PCMCIA isn't present
Date: Fri, 14 Aug 2009 22:46:25 -0700 [thread overview]
Message-ID: <4A864BB1.8020307@redfish-solutions.com> (raw)
From: Philip A Prindeville <philipp@redfish-solutions.com>
If you're building for a platform that has (for example) no PCMCIA/
Cardbus, then having a single knob to turn to disable this is a
major win. Especially if more devices get add later that are
PCMCIA-based.
Tested.
Signed-off-by: Philip A Prindeville <philipp@redfish-solutions.com>
---
config.mk | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/config.mk b/config.mk
index 0c3ea98..a24b7bd 100644
--- a/config.mk
+++ b/config.mk
@@ -191,7 +191,9 @@ CONFIG_B43=m
CONFIG_B43_HWRNG=y
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
+ifneq ($(CONFIG_PCMCIA),)
CONFIG_B43_PCMCIA=y
+endif
CONFIG_B43_PIO=y
CONFIG_B43_LEDS=y
CONFIG_B43_RFKILL=y
@@ -242,8 +244,10 @@ CONFIG_SSB_BLOCKIO=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_B43_PCI_BRIDGE=y
+ifneq ($(CONFIG_PCMCIA),)
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
CONFIG_SSB_PCMCIAHOST=y
+endif
# CONFIG_SSB_DEBUG=y
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
@@ -258,7 +262,9 @@ CONFIG_B44_PCI=y
CONFIG_RTL8180=m
CONFIG_ADM8211=m
+ifneq ($(CONFIG_PCMCIA),)
CONFIG_PCMCIA_ATMEL=m
+endif
CONFIG_RT2X00_LIB_PCI=m
CONFIG_RT2400PCI=m
next reply other threads:[~2009-08-15 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 5:46 Philip A. Prindeville [this message]
2009-08-18 23:34 ` [PATCH] Don't build PCMCIA modules when PCMCIA isn't present Luis R. Rodriguez
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=4A864BB1.8020307@redfish-solutions.com \
--to=philipp@redfish-solutions.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.