From: Kalle Valo <kvalo@codeaurora.org>
To: Karthikeyan Periyasamy <periyasa@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: fix duplication peer create on same radio
Date: Tue, 14 Apr 2020 08:10:09 +0000 (UTC) [thread overview]
Message-ID: <20200414081009.0F0E0C432C2@smtp.codeaurora.org> (raw)
In-Reply-To: <1586343795-21422-1-git-send-email-periyasa@codeaurora.org>
Karthikeyan Periyasamy <periyasa@codeaurora.org> wrote:
> Add the pdev index information in the peer object to validate
> the peer creation. Ignore the peer creation request, if the given
> MAC address is already present in the peer list with same radio.
> If we allow the peer creation in above scenario, FW assert will happen.
> Above scenario occurred in two cases, where Multiple AP VAP created in
> the same radio.
>
> 1. when testing tool sends association request to two AP with same
> MAC address
> 2. when a station do roaming from one AP VAP to another AP VAP.
>
> Signed-off-by: Karthikeyan Periyasamy <periyasa@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
1e744bf218b5 ath11k: fix duplication peer create on same radio
--
https://patchwork.kernel.org/patch/11479785/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2020-04-14 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 11:03 [PATCH] ath11k: fix duplication peer create on same radio Karthikeyan Periyasamy
2020-04-08 11:03 ` Karthikeyan Periyasamy
2020-04-14 8:10 ` Kalle Valo
2020-04-14 8:10 ` Kalle Valo [this message]
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=20200414081009.0F0E0C432C2@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=periyasa@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.