From: Peter Oh <poh@qca.qualcomm.com>
To: <ath10k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: [PATCH v2 0/4] ath10k: rename mesh and add abstraction layer
Date: Thu, 28 Jan 2016 13:54:06 -0800 [thread overview]
Message-ID: <cover.1454015989.git.poh@qca.qualcomm.com> (raw)
Split Mesh service to 11s Mesh and non-11s Mesh according to
firmware service bit to help users distinguish 11s Mesh from
non 11s Mesh.
And add abstraction layer for vdev subtype to solve subtype mismatch
and to give flexible compatibility among different firmware revisions.
v2:
* Rebased. No code changes.
Peter Oh (4):
ath10k: rename Mesh related service names
ath10k: update 10.4 WMI service map
ath10k: use vif->type and vif->p2p for P2P_GO check
ath10k: add abstraction layer for vdev subtype
drivers/net/wireless/ath/ath10k/mac.c | 25 +++++------
drivers/net/wireless/ath/ath10k/wmi-ops.h | 11 +++++
drivers/net/wireless/ath/ath10k/wmi-tlv.c | 1 +
drivers/net/wireless/ath/ath10k/wmi.c | 72 ++++++++++++++++++++++++++++++-
drivers/net/wireless/ath/ath10k/wmi.h | 67 ++++++++++++++++++++++------
5 files changed, 151 insertions(+), 25 deletions(-)
--
1.9.1
next reply other threads:[~2016-01-28 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 21:54 Peter Oh [this message]
2016-01-28 21:54 ` [PATCH v2 1/4] ath10k: rename Mesh related service names Peter Oh
2016-01-28 21:54 ` [PATCH v2 2/4] ath10k: update 10.4 WMI service map Peter Oh
2016-01-28 21:54 ` [PATCH v2 3/4] ath10k: use vif->type and vif->p2p for P2P_GO check Peter Oh
2016-01-28 21:54 ` [PATCH v2 4/4] ath10k: add abstraction layer for vdev subtype Peter Oh
2016-02-24 13:51 ` [PATCH v2 0/4] ath10k: rename mesh and add abstraction layer 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=cover.1454015989.git.poh@qca.qualcomm.com \
--to=poh@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--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).