From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC v4] cfg80211: Android P2P-Device workaround
Date: Mon, 29 Apr 2013 15:53:46 +0200 [thread overview]
Message-ID: <1367243626.8289.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <517E7ABD.9000505@broadcom.com>
On Mon, 2013-04-29 at 15:50 +0200, Arend van Spriel wrote:
> > This is a hack to provide it so not only is Android happy
> > but also the current version of wpa_supplicant can work
> > with P2P-Device functionality without needing changes to
> > support the P2P-Device commands, just a little bit to not
> > attempt to change the interface type to station.
>
> Reading the subject I was going to say it is not only Android
> workaround, but the commit message also covers non-android use-case.
>
> I will give it another spin. What changed compared to v3.
The nl80211 events got the ifindex, that got removed when I changed from
wdev->netdev to wdev->p2pdev (for you ;-) ) so the scan and other events
didn't have the right information for a hacked wpa_supplicant that isn't
aware of wdev IDs.
johannes
next prev parent reply other threads:[~2013-04-29 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 12:26 [RFC v4] cfg80211: Android P2P-Device workaround Johannes Berg
2013-04-29 13:50 ` Arend van Spriel
2013-04-29 13:53 ` Johannes Berg [this message]
2013-04-29 16:32 ` Marcel Holtmann
2013-04-30 13:38 ` Sreenath
2013-04-30 13:43 ` Johannes Berg
2013-05-02 10:03 ` Arend van Spriel
2013-05-02 10:06 ` Johannes Berg
2013-05-02 19:17 ` Arend van Spriel
2013-05-07 10:20 ` Johannes Berg
2013-05-23 3:18 ` YanBo
2013-05-23 9:40 ` Johannes Berg
2013-05-23 14:40 ` YanBo
2013-05-23 16:08 ` Johannes Berg
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=1367243626.8289.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.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).