All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Venkateswara Naralasetty <vnaralas@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: fix wmi peer flags in peer assoc command
Date: Mon, 15 Jun 2020 14:34:27 +0000 (UTC)	[thread overview]
Message-ID: <20200615143427.260A5C433CB@smtp.codeaurora.org> (raw)
In-Reply-To: <1591771841-25503-1-git-send-email-vnaralas@codeaurora.org>

Venkateswara Naralasetty <vnaralas@codeaurora.org> wrote:

> Currently need ptk/gtk wmi peer flags in wmi peer assoc cmd
> are set based on the rsnie and wpaie of the bss from the bss list.
> Since this bss list is not updated with current BSSID for AP mode,
> we may not find bss from the bss list. Which results in ptk/gtk peer
> flags are not set in the wmi peer assoc cmd. Due to this EAPOL frames
> are going in data rates instead of management rates.
> 
> Tested-on: IPQ8074 WLAN.HK.2.1.0.1-01228-QCAHKSWPL_SILICONZ-1
> 
> Signed-off-by: Venkateswara Naralasetty <vnaralas@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

Patch applied to ath-next branch of ath.git, thanks.

01e34233c645 ath11k: fix wmi peer flags in peer assoc command

-- 
https://patchwork.kernel.org/patch/11597241/

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


_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2020-06-15 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  6:50 [PATCH] ath11k: fix wmi peer flags in peer assoc command Venkateswara Naralasetty
2020-06-10  6:50 ` Venkateswara Naralasetty
2020-06-15 14:34 ` Kalle Valo [this message]
2020-06-15 14:34 ` Kalle Valo

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=20200615143427.260A5C433CB@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vnaralas@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.