From: "John W. Linville" <linville@tuxdriver.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@redhat.com>,
David Spinadel <david.spinadel@intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: P2P support in brcmfmac
Date: Wed, 27 Mar 2013 11:10:53 -0400 [thread overview]
Message-ID: <20130327151053.GD2146@tuxdriver.com> (raw)
In-Reply-To: <5153082B.6080000@broadcom.com>
On Wed, Mar 27, 2013 at 03:54:35PM +0100, Arend van Spriel wrote:
> On 03/27/2013 03:38 PM, Johannes Berg wrote:
> > Or you could just remove the module parameter *and* advertisting the
> > P2P_DEVICE interface type, that would be a very small patch to "fix" the
> > API by disabling it for that kernel version. OTOH, I'm not sure if
> > that's a concern for you. For me, it wouldn't be a concern because we
> > mostly use compat-wireless anyway, but your situation might be
> > different.
>
> That is indeed what I guessed the patch should look like, which would
> make P2P unavailable for 3.9 regardless the wpa_supplicant version used.
> But indeed there is always compat-drivers aka. compat-wireless so I am
> not that concerned.
I think this is the patch we need in order to avoid messy confusion later...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-03-27 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 11:51 P2P support in brcmfmac Arend van Spriel
2013-03-27 12:22 ` John W. Linville
2013-03-27 12:34 ` Johannes Berg
2013-03-27 12:44 ` John W. Linville
2013-03-27 12:51 ` Johannes Berg
2013-03-27 13:04 ` John W. Linville
2013-03-27 14:29 ` Arend van Spriel
2013-03-27 14:38 ` Johannes Berg
2013-03-27 14:54 ` Arend van Spriel
2013-03-27 15:10 ` John W. Linville [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=20130327151053.GD2146@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arend@broadcom.com \
--cc=david.spinadel@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@redhat.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 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.