From: <gregkh@suse.de>
To: randy.dunlap@oracle.com, gregkh@suse.de,
linux-kernel@vger.kernel.org, sfr@canb.auug.org.au
Subject: patch staging-vt66-kconfig-depends-on-wlan.patch added to gregkh-2.6 tree
Date: Fri, 18 Dec 2009 11:34:00 -0800 [thread overview]
Message-ID: <12611648401355@kroah.org> (raw)
In-Reply-To: <20091214084446.8346f39c.randy.dunlap@oracle.com>
This is a note to let you know that I've just added the patch titled
Subject: Staging/vt66*: kconfig, depends on WLAN
to my gregkh-2.6 tree. Its filename is
staging-vt66-kconfig-depends-on-wlan.patch
This tree can be found at
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/
>From randy.dunlap@oracle.com Fri Dec 18 10:31:37 2009
From: Randy Dunlap <randy.dunlap@oracle.com>
Date: Mon, 14 Dec 2009 08:44:46 -0800
Subject: Staging/vt66*: kconfig, depends on WLAN
To: Stephen Rothwell <sfr@canb.auug.org.au>, gregkh@suse.de
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Message-ID: <20091214084446.8346f39c.randy.dunlap@oracle.com>
From: Randy Dunlap <randy.dunlap@oracle.com>
The vt665[56] drivers can be built when CONFIG_NET=n &
CONFIG_NETDEVICES=n or just when CONFIG_WLAN=n.
This leads to build failures.
Prevent this by making them depend on WLAN.
[This patch was lost in a dualing trees merge;
still needs to be re-applied.]
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
drivers/staging/vt6655/Kconfig | 2 +-
drivers/staging/vt6656/Kconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- a/drivers/staging/vt6655/Kconfig
+++ b/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---
--- a/drivers/staging/vt6656/Kconfig
+++ b/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-12-18 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 5:59 linux-next: Tree for December 14 Stephen Rothwell
2009-12-14 16:44 ` [PATCH] staging/vt66*: kconfig, depends on WLAN Randy Dunlap
2009-12-18 19:34 ` gregkh [this message]
2009-12-14 17:08 ` [PATCH -next] radio/si470x: #include <sched.h> Randy Dunlap
2009-12-14 17:10 ` [PATCH -next] fs: fix compat_ioctl build for CONFIG_BLOCK=n Randy Dunlap
2009-12-14 20:16 ` Arnd Bergmann
2009-12-15 19:29 ` Randy Dunlap
2009-12-14 19:06 ` linux-next: Tree for December 14 (nouveau & AGP) Randy Dunlap
2009-12-14 19:51 ` [PATCH -next] nouveau: fix ch7006 build 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=12611648401355@kroah.org \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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.