From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, devel@driverdev•osuosl.org
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
gregkh@suse•de
Subject: [PATCH -next] staging/vt665*: depends on WLAN
Date: Wed, 11 Nov 2009 09:31:31 -0800 [thread overview]
Message-ID: <20091111093131.66e7f4ec.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091111203159.a2a6eeeb.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle•com>
The vt665[56] drivers can be built when CONFIG_NET=n &
CONFIG_NETDEVICES=n. This leads to build failures.
Prevent this by making them depend on WLAN.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
---
drivers/staging/vt6655/Kconfig | 2 +-
drivers/staging/vt6656/Kconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20091110.orig/drivers/staging/vt6655/Kconfig
+++ linux-next-20091110/drivers/staging/vt6655/Kconfig
@@ -1,6 +1,6 @@
config VT6655
tristate "VIA Technologies VT6655 support"
- depends on PCI
+ depends on PCI && WLAN
select WIRELESS_EXT
select WEXT_PRIV
---help---
--- linux-next-20091110.orig/drivers/staging/vt6656/Kconfig
+++ linux-next-20091110/drivers/staging/vt6656/Kconfig
@@ -1,6 +1,6 @@
config VT6656
tristate "VIA Technologies VT6656 support"
- depends on USB
+ depends on USB && WLAN
select WIRELESS_EXT
select WEXT_PRIV
---help---
next prev parent reply other threads:[~2009-11-11 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 9:31 linux-next: Tree for November 11 Stephen Rothwell
2009-11-11 17:31 ` [PATCH -next] pcmcia: fix printk formats Randy Dunlap
2009-11-11 18:27 ` Dominik Brodowski
2009-11-11 17:31 ` [PATCH -next] staging/rtl8192u: depends on USB Randy Dunlap
2009-11-11 17:31 ` Randy Dunlap [this message]
2009-11-11 17:31 ` [PATCH -next] staging/vt665*: fix printk formats Randy Dunlap
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=20091111093131.66e7f4ec.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=devel@driverdev$(echo .)osuosl.org \
--cc=gregkh@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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