From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Stanislav Yakovlev <stas.yakovlev@gmail.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] ipw2200: select CFG80211_WEXT
Date: Tue, 23 Dec 2014 12:55:11 +0200 [thread overview]
Message-ID: <87oaqueiuo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1419330521.6091.1.camel@sipsolutions.net> (Johannes Berg's message of "Tue, 23 Dec 2014 11:28:41 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Mon, 2014-12-22 at 19:10 +0100, Paul Bolle wrote:
>> Commit 24a0aa212ee2 ("cfg80211: make WEXT compatibility unselectable")
>> made it impossible to depend on CFG80211_WEXT. It does still allow to
>> select that symbol. (Yes, the commit summary is confusing.)
>>
>> So make IPW2200 select CFG80211_WEXT, so that the ipw2200 driver can be
>> built again.
>>
>> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
>> ---
>> Johannes,
>>
>> Building v3.19-rc1 for an outdated ThinkPad X41 left me without the
>> ipw2200 driver. It turns out this trivial patch is all that's needed to
>> make ipw2200 buildable again.
>>
>> (A similar patch would be needed for the drivers behind Kconfig symbol
>> HERMES. Ie, orinico and friends.)
>
> Yeah, config HERMES needs the same change.
>
> Kalle, do you want to take those through your tree, or should I fix it
> seeing that I introduced the bug in a sense?
To keep things simple I would prefer to take this through
wireless-drivers.git, if it's ok for you.
--
Kalle Valo
next prev parent reply other threads:[~2014-12-23 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 18:10 [PATCH RFC] ipw2200: select CFG80211_WEXT Paul Bolle
2014-12-22 19:13 ` Johannes Berg
2014-12-23 6:52 ` Kalle Valo
2014-12-23 10:20 ` Paul Bolle
2014-12-23 10:50 ` Kalle Valo
2014-12-23 10:28 ` Johannes Berg
2014-12-23 10:55 ` Kalle Valo [this message]
2014-12-24 13:18 ` Kalle Valo
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=87oaqueiuo.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=stas.yakovlev@gmail.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;
as well as URLs for NNTP newsgroup(s).