From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
linux-wireless@vger.kernel.org
Cc: Kalle Valo <kvalo@codeaurora.org>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com,
Amitkumar Karwar <amitkarwar@gmail.com>,
Ganapathi Bhat <ganapathi.bhat@nxp.com>,
Xinming Hu <huxinming820@gmail.com>,
Igor Mitsyanko <imitsyanko@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>,
Sergey Matyukevich <smatyukevich@quantenna.com>
Subject: Re: [PATCH v2] cfg80211: change internal management frame registration API
Date: Sat, 18 Apr 2020 22:40:51 +0200 [thread overview]
Message-ID: <04a2ef8ec78815779fd36f98a134e1f9c4b900c2.camel@sipsolutions.net> (raw)
In-Reply-To: <1718a2f5ce0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (sfid-20200418_000902_720641_98B61D53)
On Sat, 2020-04-18 at 00:08 +0200, Arend Van Spriel wrote:
> On April 17, 2020 12:43:09 PM Johannes Berg <johannes@sipsolutions.net> wrote:
>
> > From: Johannes Berg <johannes.berg@intel.com>
> >
> > Almost all drivers below cfg80211 get the API wrong (except for
> > cfg80211)
Oops, now that I re-read this, of course that latter "cfg80211" should
be "mac80211".
johannes
next prev parent reply other threads:[~2020-04-18 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 10:43 [PATCH v2] cfg80211: change internal management frame registration API Johannes Berg
2020-04-17 22:08 ` Arend Van Spriel
2020-04-18 20:40 ` Johannes Berg [this message]
2020-04-19 20:47 ` Sergey Matyukevich
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=04a2ef8ec78815779fd36f98a134e1f9c4b900c2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amitkarwar@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=avinashp@quantenna.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=ganapathi.bhat@nxp.com \
--cc=hante.meuleman@broadcom.com \
--cc=huxinming820@gmail.com \
--cc=imitsyanko@quantenna.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=smatyukevich@quantenna.com \
--cc=wright.feng@cypress.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