From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: vt665x depend on WIRELESS
Date: Fri, 18 Dec 2009 10:53:03 -0800 [thread overview]
Message-ID: <20091218185303.GA23226@suse.de> (raw)
In-Reply-To: <20091218094552.f06aad32.randy.dunlap@oracle.com>
On Fri, Dec 18, 2009 at 09:45:52AM -0800, Randy Dunlap wrote:
> On Fri, 18 Dec 2009 20:23:08 +0300 Alexander Beregalov wrote:
>
> > Fix build error when NET or/and WIRELESS are not enabled.
> >
> > Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
> > ---
> > drivers/staging/vt6655/Kconfig | 2 +-
> > drivers/staging/vt6656/Kconfig | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/vt6655/Kconfig b/drivers/staging/vt6655/Kconfig
> > index 825bbc4..6a186be 100644
> > --- 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 && WIRELESS
> > select WIRELESS_EXT
> > select WEXT_PRIV
> > ---help---
> > diff --git a/drivers/staging/vt6656/Kconfig b/drivers/staging/vt6656/Kconfig
> > index 87bcd26..6fceae4 100644
> > --- 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 && WIRELESS
> > select WIRELESS_EXT
> > select WEXT_PRIV
> > ---help---
> > --
>
> depends on WLAN
>
> would be better, and the patch has already been submitted to Greg...
> I don't know where it is in his "system" though.
It just got applied :)
thanks,
greg k-h
prev parent reply other threads:[~2009-12-18 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 17:23 [PATCH] Staging: vt665x depend on WIRELESS Alexander Beregalov
2009-12-18 17:45 ` Randy Dunlap
2009-12-18 18:53 ` Greg KH [this message]
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=20091218185303.GA23226@suse.de \
--to=gregkh@suse.de \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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