From: Randy Dunlap <randy.dunlap@oracle.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ps3_gelic_wireless: Fix build failure due to missing WEXT_PRIV
Date: Fri, 18 Dec 2009 08:55:47 -0800 [thread overview]
Message-ID: <20091218085547.fb8bdaf5.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1261115574.2173.18.camel@pasglop>
On Fri, 18 Dec 2009 16:52:54 +1100 Benjamin Herrenschmidt wrote:
> The option to support the old style PSK interface in the PS3
> GELIC wireless drivers requires CONFIG_WEXT_PRIV to be set
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> Please send to Linus asap (or I can put it in powerpc.git) as it's
> breaking one of my test build configs :-)
>
> diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
> index e58a653..c0ecc77 100644
> --- a/drivers/net/Kconfig
> +++ b/drivers/net/Kconfig
> @@ -2358,6 +2358,7 @@ config GELIC_WIRELESS
> config GELIC_WIRELESS_OLD_PSK_INTERFACE
> bool "PS3 Wireless private PSK interface (OBSOLETE)"
> depends on GELIC_WIRELESS
> + select WEXT_PRIV
> help
> This option retains the obsolete private interface to pass
> the PSK from user space programs to the driver. The PSK
Probably also needs
depends on WLAN
to prevent build failures.
---
~Randy
next prev parent reply other threads:[~2009-12-18 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 5:52 [PATCH] ps3_gelic_wireless: Fix build failure due to missing WEXT_PRIV Benjamin Herrenschmidt
2009-12-18 16:55 ` Randy Dunlap [this message]
2009-12-18 18:24 ` [PATCH v2] " Geoff Levand
2009-12-18 18:30 ` Johannes Berg
2009-12-18 19:01 ` Geoff Levand
2009-12-18 22:09 ` Benjamin Herrenschmidt
2009-12-18 22:09 ` [PATCH] " Benjamin Herrenschmidt
2009-12-18 19:19 ` [PATCH v3] " Geoff Levand
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=20091218085547.fb8bdaf5.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=benh@kernel.crashing.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).