From: Kalle Valo <kvalo@codeaurora.org>
To: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH 1/4] ath11k: reset qos control bit after stripping qos field in iee80211_hdr
Date: Wed, 29 May 2019 15:21:10 +0000 (UTC) [thread overview]
Message-ID: <20190529152110.8E47E6087B@smtp.codeaurora.org> (raw)
In-Reply-To: <1559080376-26817-2-git-send-email-pradeepc@codeaurora.org>
Pradeep Kumar Chitrapu <pradeepc@codeaurora.org> wrote:
> fix resetting qos control bit in frame control when qos control field
> is stripped from native wifi packet.
>
> Signed-off-by: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>
4 patches applied to ath.git, thanks.
e10d09bc1c2f ath11k: reset qos control bit after stripping qos field in iee80211_hdr
291848e1edc1 ath11k: pad mic len for protected action frames
28c2a93e7c41 ath11k: fix multicast txrx for secure 11s mesh support
5710b3f7f0f9 ath11k: fix action frame rx processing
--
https://patchwork.kernel.org/patch/10965859/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-05-29 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 21:52 [PATCH 0/4] ath11k: enable 11s secured mesh support Pradeep Kumar Chitrapu
2019-05-28 21:52 ` [PATCH 1/4] ath11k: reset qos control bit after stripping qos field in iee80211_hdr Pradeep Kumar Chitrapu
2019-05-29 15:21 ` Kalle Valo [this message]
2019-05-28 21:52 ` [PATCH 2/4] ath11k: pad mic len for protected action frames Pradeep Kumar Chitrapu
2019-05-28 21:52 ` [PATCH 3/4] ath11k: fix multicast txrx for secure 11s mesh support Pradeep Kumar Chitrapu
2019-05-28 21:52 ` [PATCH 4/4] ath11k: fix action frame rx processing Pradeep Kumar Chitrapu
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=20190529152110.8E47E6087B@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=pradeepc@codeaurora.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 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.