From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <ath12k@lists.infradead.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: [PATCH 0/4] wifi: ath: Cleanup WMI peer flags
Date: Mon, 6 Nov 2023 10:26:02 -0800 [thread overview]
Message-ID: <20231106-ath-peer-flags-v1-0-781e83b7e8e8@quicinc.com> (raw)
Both ath11k and ath12k inherited from ath10k some WMI peer flag
definitions that are unused, so remove them.
This series is compile tested only.
Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
---
Jeff Johnson (4):
wifi: ath11k: Remove obsolete struct wmi_peer_flags_map *peer_flags
wifi: ath12k: Remove obsolete struct wmi_peer_flags_map *peer_flags
wifi: ath11k: Consolidate WMI peer flags
wifi: ath12k: Consolidate WMI peer flags
drivers/net/wireless/ath/ath11k/wmi.h | 61 ++++++++++-----------------------
drivers/net/wireless/ath/ath12k/wmi.h | 63 +++++++++++------------------------
2 files changed, 37 insertions(+), 87 deletions(-)
---
base-commit: ac2f43d3d34e52b0d388b4c573ff6bbac90235b9
change-id: 20231102-ath-peer-flags-824af380270b
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next reply other threads:[~2023-11-06 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 18:26 Jeff Johnson [this message]
2023-11-06 18:26 ` [PATCH 1/4] wifi: ath11k: Remove obsolete struct wmi_peer_flags_map *peer_flags Jeff Johnson
2023-11-22 18:25 ` Kalle Valo
2023-11-06 18:26 ` [PATCH 2/4] wifi: ath12k: " Jeff Johnson
2023-11-06 18:26 ` [PATCH 3/4] wifi: ath11k: Consolidate WMI peer flags Jeff Johnson
2023-11-06 18:26 ` [PATCH 4/4] wifi: ath12k: " Jeff Johnson
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=20231106-ath-peer-flags-v1-0-781e83b7e8e8@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).