From: Kalle Valo <kvalo@kernel.org>
To: Aloka Dixit <quic_alokad@quicinc.com>
Cc: Wen Gong <quic_wgong@quicinc.com>, <ath12k@lists.infradead.org>,
<linux-wireless@vger.kernel.org>,
Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
Subject: Re: [PATCH v5 06/11] wifi: ath12k: prepare EHT peer assoc parameters
Date: Thu, 03 Aug 2023 11:59:40 +0300 [thread overview]
Message-ID: <87v8dwtsar.fsf@kernel.org> (raw)
In-Reply-To: <eac30246-1360-2854-3f53-28bdf5a24e24@quicinc.com> (Aloka Dixit's message of "Thu, 27 Jul 2023 09:59:14 -0700")
Aloka Dixit <quic_alokad@quicinc.com> writes:
> On 7/26/2023 10:48 PM, Wen Gong wrote:
>
>> On 7/27/2023 12:38 AM, Aloka Dixit wrote:
>>> On 7/25/2023 8:43 PM, Wen Gong wrote:
>>>> On 7/26/2023 6:40 AM, Aloka Dixit wrote:
>>>> [...]
>>>>> +
>>>>> +static void ath12k_peer_assoc_h_eht(struct ath12k *ar,
>>>>> + struct ieee80211_vif *vif,
>>>>> + struct ieee80211_sta *sta,
>>>>> + struct ath12k_wmi_peer_assoc_arg *arg)
>>>>> +{
>>>>> +
>>>> This is the IEs of my AP below, then it will still entered into
>>>> this branch for my ath12k station mode.
>>>> sta->deflink.eht_cap and sta->deflink.he_cap is copied from peer
>>>> remote, for ath12k station mode, peer
>>>> remote is the AP. The field only_20mhz is only valid when the IEs
>>>> is from a station which only support
>>>> 20 MHz.
>>>>
>>>> I think the flag from_ap should be added here as well as function
>>>> ieee80211_eht_mcs_nss_size().
>>>>
>>>> Please correct me if wrong.
>>>>
>>>
>>> Okay, can you fix this in a follow-up patch?
>>> I don't have a device to test the station mode to verify a fix.
>>> Thanks.
>> The fix patch is simple like this (I have verified OK), you can
>> merge it to your patch.😁
>> It is to not use only_20mhz when ath12k is station mode.
Wen, please submit a follow-up patch which explains the situation
clearly. The reasoning for your change is not obvious for me. Also
consider if there should be a comment in the code.
> Every time I re-base the series I have to test, add cover-letter,
> change-log in 11 patches.
BTW you don't need to add a changelog on every patch. IMHO it's a lot
easier for everyone if all the changes are listed in the cover letter,
no need repeat that information in individual patches.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath12k mailing list
ath12k@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/ath12k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Aloka Dixit <quic_alokad@quicinc.com>
Cc: Wen Gong <quic_wgong@quicinc.com>, <ath12k@lists.infradead.org>,
<linux-wireless@vger.kernel.org>,
Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
Subject: Re: [PATCH v5 06/11] wifi: ath12k: prepare EHT peer assoc parameters
Date: Thu, 03 Aug 2023 11:59:40 +0300 [thread overview]
Message-ID: <87v8dwtsar.fsf@kernel.org> (raw)
In-Reply-To: <eac30246-1360-2854-3f53-28bdf5a24e24@quicinc.com> (Aloka Dixit's message of "Thu, 27 Jul 2023 09:59:14 -0700")
Aloka Dixit <quic_alokad@quicinc.com> writes:
> On 7/26/2023 10:48 PM, Wen Gong wrote:
>
>> On 7/27/2023 12:38 AM, Aloka Dixit wrote:
>>> On 7/25/2023 8:43 PM, Wen Gong wrote:
>>>> On 7/26/2023 6:40 AM, Aloka Dixit wrote:
>>>> [...]
>>>>> +
>>>>> +static void ath12k_peer_assoc_h_eht(struct ath12k *ar,
>>>>> + struct ieee80211_vif *vif,
>>>>> + struct ieee80211_sta *sta,
>>>>> + struct ath12k_wmi_peer_assoc_arg *arg)
>>>>> +{
>>>>> +
>>>> This is the IEs of my AP below, then it will still entered into
>>>> this branch for my ath12k station mode.
>>>> sta->deflink.eht_cap and sta->deflink.he_cap is copied from peer
>>>> remote, for ath12k station mode, peer
>>>> remote is the AP. The field only_20mhz is only valid when the IEs
>>>> is from a station which only support
>>>> 20 MHz.
>>>>
>>>> I think the flag from_ap should be added here as well as function
>>>> ieee80211_eht_mcs_nss_size().
>>>>
>>>> Please correct me if wrong.
>>>>
>>>
>>> Okay, can you fix this in a follow-up patch?
>>> I don't have a device to test the station mode to verify a fix.
>>> Thanks.
>> The fix patch is simple like this (I have verified OK), you can
>> merge it to your patch.😁
>> It is to not use only_20mhz when ath12k is station mode.
Wen, please submit a follow-up patch which explains the situation
clearly. The reasoning for your change is not obvious for me. Also
consider if there should be a comment in the code.
> Every time I re-base the series I have to test, add cover-letter,
> change-log in 11 patches.
BTW you don't need to add a changelog on every patch. IMHO it's a lot
easier for everyone if all the changes are listed in the cover letter,
no need repeat that information in individual 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-08-03 8:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 22:40 [PATCH v5 00/11] wifi: ath12k: (v5) EHT support Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 01/11] wifi: ath12k: rename HE capabilities setup/copy functions Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-08-03 9:12 ` Kalle Valo
2023-08-03 9:12 ` Kalle Valo
2023-07-25 22:40 ` [PATCH v5 02/11] wifi: ath12k: move HE capabilities processing to a new function Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 03/11] wifi: ath12k: WMI support to process EHT capabilities Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 04/11] wifi: ath12k: propagate EHT capabilities to userspace Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 05/11] wifi: ath12k: add EHT PHY modes Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 06/11] wifi: ath12k: prepare EHT peer assoc parameters Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-26 3:43 ` Wen Gong
2023-07-26 3:43 ` Wen Gong
2023-07-26 16:38 ` Aloka Dixit
2023-07-26 16:38 ` Aloka Dixit
2023-07-27 5:48 ` Wen Gong
2023-07-27 5:48 ` Wen Gong
2023-07-27 16:59 ` Aloka Dixit
2023-07-27 16:59 ` Aloka Dixit
2023-07-28 2:50 ` Wen Gong
2023-07-28 2:50 ` Wen Gong
2023-08-03 8:59 ` Kalle Valo [this message]
2023-08-03 8:59 ` Kalle Valo
2023-07-25 22:40 ` [PATCH v5 07/11] wifi: ath12k: add WMI support for EHT peer Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 08/11] wifi: ath12k: peer assoc for 320 MHz Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 09/11] wifi: ath12k: add MLO header in peer association Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 10/11] wifi: ath12k: parse WMI service ready ext2 event Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
2023-07-25 22:40 ` [PATCH v5 11/11] wifi: ath12k: configure puncturing bitmap Aloka Dixit
2023-07-25 22:40 ` Aloka Dixit
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=87v8dwtsar.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 \
--cc=quic_wgong@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 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.