From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Ritesh Singh <ritesi@codeaurora.org>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH 3/3] ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references
Date: Tue, 09 Jun 2020 17:46:37 +0530 [thread overview]
Message-ID: <0fdcc91bc6e9ffd7d924e306895cf903@codeaurora.org> (raw)
In-Reply-To: <87tuzkmosd.fsf@codeaurora.org>
On 2020-06-09 17:31, Kalle Valo wrote:
> Maharaja Kennadyrajan <mkenna@codeaurora.org> writes:
>
>> On 2020-05-28 13:00, Kalle Valo wrote:
>>> Maharaja Kennadyrajan <mkenna@codeaurora.org> wrote:
>>>
>>>> Unused structure ath11k_vdev_stop_status is removed.
>>>> 'ath11k_mac_get_ar_vdev_stop_status' api has been replaced
>>>> with 'ath11k_mac_get_ar_by_vdev_id' inside vdev_stopped_event.
>>>>
>>>> Tested-on: IPQ8074 WLAN.HK.2.4.0.1-00009-QCAHKSWPL_SILICONZ-1
>>>>
>>>> Signed-off-by: Ritesh Singh <ritesi@codeaurora.org>
>>>> Signed-off-by: Maharaja Kennadyrajan <mkenna@codeaurora.org>
>>>> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
>>>
>>> What about other firmware branches? For example, will this break
>>> 2.1.0.1 branch support?
>>
>> [Maha]: It won't break 2.1.0.1 branch as it is host related change.
>
> What do you mean with "host related changed" exactly? In patch 1 I see
> that you add a new handler for WMI_VDEV_DELETE_RESP_EVENTID event. So
> firmware functionality is very much involved here, right? For example,
> do all branches send that event to the host?
[Maha]: You are right, Stop event will come for all the firmware.
So, it won't break with other firmware branches.
we just replaced the ath11k_mac_get_ar_vdev_stop_status by
ath11k_mac_get_ar_by_vdev_id.
Regards,
Maha
next prev parent reply other threads:[~2020-06-09 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 13:30 [PATCH 0/3] ath11k: vdev and peer delete synchronization with firmware Maharaja Kennadyrajan
2020-05-21 13:30 ` [PATCH 1/3] ath11k: vdev " Maharaja Kennadyrajan
2020-11-10 18:28 ` Kalle Valo
[not found] ` <20201110182825.3D1C6C433FE@smtp.codeaurora.org>
2020-11-11 5:29 ` Maharaja Kennadyrajan
2020-05-21 13:30 ` [PATCH 2/3] ath11k: peer " Maharaja Kennadyrajan
2020-05-21 13:30 ` [PATCH 3/3] ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references Maharaja Kennadyrajan
2020-05-28 7:30 ` Kalle Valo
[not found] ` <20200528073034.F14B9C43387@smtp.codeaurora.org>
2020-06-09 11:54 ` Maharaja Kennadyrajan
2020-06-09 12:01 ` Kalle Valo
2020-06-09 12:16 ` Maharaja Kennadyrajan [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-12 7:42 [PATCH v2 0/3] ath11k: vdev and peer delete synchronization with firmware Maharaja Kennadyrajan
2020-11-12 7:43 ` [PATCH 3/3] ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references Maharaja Kennadyrajan
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=0fdcc91bc6e9ffd7d924e306895cf903@codeaurora.org \
--to=mkenna@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ritesi@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 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).