From: Kalle Valo <kvalo@kernel.org>
To: Aloka Dixit <quic_alokad@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
Subject: Re: [PATCH v3 03/11] wifi: ath12k: process EHT capabilities
Date: Mon, 17 Apr 2023 16:01:14 +0300 [thread overview]
Message-ID: <87h6tewtlx.fsf@kernel.org> (raw)
In-Reply-To: <20230413215156.2649-4-quic_alokad@quicinc.com> (Aloka Dixit's message of "Thu, 13 Apr 2023 14:51:48 -0700")
Aloka Dixit <quic_alokad@quicinc.com> writes:
> Add WMI support to process the EHT capabilities passed by the firmware.
> Add required EHT specific definitions in structures ath12k_band_cap and
> ath12k_wmi_svc_rdy_ext_parse.
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1
> Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
> Signed-off-by: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
This had a new warning:
drivers/net/wireless/ath/ath12k/wmi.c:4072: line length of 97 exceeds 90 columns
I fixed that in the pending branch. But please use ath12k-check before
you submit the patches.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-04-17 13:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 21:51 [PATCH v3 00/11] wifi: ath12k: (v3) EHT support Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 01/11] wifi: ath12k: rename HE capabilities setup/copy functions Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 02/11] wifi: ath12k: move HE capabilities processing to a new function Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 03/11] wifi: ath12k: process EHT capabilities Aloka Dixit
2023-04-17 13:01 ` Kalle Valo [this message]
2023-04-13 21:51 ` [PATCH v3 04/11] wifi: ath12k: propagate EHT capabilities to userspace Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 05/11] wifi: ath12k: add EHT PHY modes Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 06/11] wifi: ath12k: prepare EHT peer assoc parameters Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 07/11] wifi: ath12k: add WMI support for EHT peer Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 08/11] wifi: ath12k: peer assoc for 320 MHz Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 09/11] wifi: ath12k: add MLO header in peer association Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 10/11] wifi: ath12k: parse WMI service ready ext2 event Aloka Dixit
2023-04-13 21:51 ` [PATCH v3 11/11] wifi: ath12k: configure puncturing bitmap Aloka Dixit
2023-04-26 6:03 ` [PATCH v3 00/11] wifi: ath12k: (v3) EHT support Kalle Valo
2023-04-26 16:49 ` Aloka Dixit
2023-04-28 21:50 ` Aloka Dixit
2023-05-05 3:09 ` Wen Gong
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=87h6tewtlx.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_alokad@quicinc.com \
--cc=quic_pradeepc@quicinc.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;
as well as URLs for NNTP newsgroup(s).