From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "grzegorz.bajorski@tieto.com" <grzegorz.bajorski@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: deliver mgmt frames from htt to monitor vifs only
Date: Fri, 4 Mar 2016 08:47:36 +0000 [thread overview]
Message-ID: <87oaauy6ho.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1448888219-2798-1-git-send-email-grzegorz.bajorski@tieto.com> (Grzegorz Bajorski's message of "Mon, 30 Nov 2015 13:56:59 +0100")
Grzegorz Bajorski <grzegorz.bajorski@tieto.com> writes:
> Until now only WMI originating mgmt frames were
> reported to mac80211. Management frames on HTT
> were basically dropped (except frames which looked
> like management but had FCS error).
>
> To allow sniffing all frames (including offloaded
> frames) without interfering with mac80211
> operation and states a new rx_flag was introduced
> and is not being used to distinguish frames and
> classify them for mac80211.
>
> Signed-off-by: Grzegorz Bajorski <grzegorz.bajorski@tieto.com>
> ---
> depends on:
> mac80211: allow drivers to report (non-)monitor frames
Note to patchwork:
178830481eee mac80211: allow drivers to report (non-)monitor frames
Is in net-next at the moment.
--
Kalle Valo
next prev parent reply other threads:[~2016-03-04 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 12:56 [PATCH] ath10k: deliver mgmt frames from htt to monitor vifs only Grzegorz Bajorski
2015-11-30 15:46 ` kbuild test robot
2015-11-30 19:44 ` Peter Oh
2015-12-01 9:42 ` Grzegorz Bajorski
2016-03-04 8:47 ` Valo, Kalle [this message]
2016-03-11 12:12 ` Valo, Kalle
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=87oaauy6ho.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=grzegorz.bajorski@tieto.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).