From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Arend van Spriel <arend@broadcom.com>,
"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 13:34:58 +0100 [thread overview]
Message-ID: <1364387698.8388.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130327122216.GA2146@tuxdriver.com>
On Wed, 2013-03-27 at 08:22 -0400, John W. Linville wrote:
> On Wed, Mar 27, 2013 at 12:51:35PM +0100, Arend van Spriel wrote:
>
> > In 3.9 we introduced P2P support in brcmfmac which was functional using
> > current wpa_supplicant P2P support, but we did not yet support the
> > P2P_DEVICE user-space API.
> >
> > Last week I enabled that in brcmfmac testing it with wpa_supplicant
> > patches for P2P_DEVICE support from David Spinadel. So I do have a
> > couple of brcmfmac patches to make that work and would like to submit
> > those for 3.9 although it is not strictly a bug fix. Would you consider
> > taking these?
>
> That doesn't sound to me like something that would be worthy of such
> an exception.
Maybe just make a small patch to disable the other API, so we don't end
up having to support both?
johannes
next prev parent reply other threads:[~2013-03-27 12:35 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 [this message]
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
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=1364387698.8388.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=david.spinadel@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@redhat.com \
--cc=linville@tuxdriver.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).