All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Maharaja Kennadyrajan <mkenna@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Ritesh Singh <ritesi@codeaurora.org>,
	Maharaja Kennadyrajan <mkenna@codeaurora.org>
Subject: Re: [PATCH 1/3] ath11k: vdev delete synchronization with firmware
Date: Tue, 10 Nov 2020 18:28:25 +0000 (UTC)	[thread overview]
Message-ID: <20201110182825.00F97C433CB@smtp.codeaurora.org> (raw)
In-Reply-To: <1590067829-26109-2-git-send-email-mkenna@codeaurora.org>

Maharaja Kennadyrajan <mkenna@codeaurora.org> wrote:

> From: Ritesh Singh <ritesi@codeaurora.org>
> 
> When the interface is added immediately after removing the
> interface, vdev deletion in firmware might not have been
> completed.
> 
> Hence, add vdev_delete_resp_event and wait_event_timeout
> to synchronize with firmware.
> 
> 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>

Does not apply anymore, please rebase.

error: patch failed: drivers/net/wireless/ath/ath11k/wmi.c:97
error: drivers/net/wireless/ath/ath11k/wmi.c: patch does not apply
stg import: Diff does not apply cleanly

3 patches set to Changes Requested.

11562969 [1/3] ath11k: vdev delete synchronization with firmware
11562967 [2/3] ath11k: peer delete synchronization with firmware
11562971 [3/3] ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references

-- 
https://patchwork.kernel.org/project/linux-wireless/patch/1590067829-26109-2-git-send-email-mkenna@codeaurora.org/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2020-11-10 18:29 UTC|newest]

Thread overview: 22+ 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 ` Maharaja Kennadyrajan
2020-05-21 13:30 ` [PATCH 1/3] ath11k: vdev " Maharaja Kennadyrajan
2020-05-21 13:30   ` Maharaja Kennadyrajan
2020-11-10 18:28   ` Kalle Valo [this message]
2020-11-10 18:28   ` Kalle Valo
     [not found]   ` <20201110182825.3D1C6C433FE@smtp.codeaurora.org>
2020-11-11  5:29     ` Maharaja Kennadyrajan
2020-11-11  5:29       ` Maharaja Kennadyrajan
2020-05-21 13:30 ` [PATCH 2/3] ath11k: peer " Maharaja Kennadyrajan
2020-05-21 13:30   ` Maharaja Kennadyrajan
2020-05-21 13:30 ` [PATCH 3/3] ath11k: remove "ath11k_mac_get_ar_vdev_stop_status" references Maharaja Kennadyrajan
2020-05-21 13:30   ` Maharaja Kennadyrajan
2020-05-28  7:30   ` Kalle Valo
2020-05-28  7:30   ` Kalle Valo
     [not found]   ` <20200528073034.F14B9C43387@smtp.codeaurora.org>
2020-06-09 11:54     ` Maharaja Kennadyrajan
2020-06-09 11:54       ` Maharaja Kennadyrajan
2020-06-09 12:01       ` Kalle Valo
2020-06-09 12:01         ` Kalle Valo
2020-06-09 12:16         ` Maharaja Kennadyrajan
2020-06-09 12:16           ` Maharaja Kennadyrajan
2020-11-12  7:42 [PATCH v2 0/3] ath11k: vdev and peer delete synchronization with firmware Maharaja Kennadyrajan
2020-11-12  7:42 ` [PATCH 1/3] ath11k: vdev " Maharaja Kennadyrajan
2020-11-12  7:42   ` 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=20201110182825.00F97C433CB@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mkenna@codeaurora.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 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.