linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Sriram R <quic_srirrama@quicinc.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] wifi: mac80211: update rx nss for the link sta
Date: Tue, 14 Feb 2023 13:48:27 +0100	[thread overview]
Message-ID: <16d922bd32b30e1a4282dc5941c6fff3b23908ca.camel@sipsolutions.net> (raw)
In-Reply-To: <20230119221201.24287-1-quic_srirrama@quicinc.com>

On Fri, 2023-01-20 at 03:42 +0530, Sriram R wrote:
> Update nss info for the non default link stations
> which gets added during ML assoc when link stations
> gets added. For the default link sta which was added
> during auth time, the nss would be updated in the usual
> flow during set station post assoc once the capabilities
> are available.
> 
> Signed-off-by: Sriram R <quic_srirrama@quicinc.com>
> ---
> v2: added wifi prefix in commit title
>  net/mac80211/cfg.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/net/mac80211/cfg.c b/net/mac80211/cfg.c
> index 72df8c708a2d..0fdf92e1428f 100644
> --- a/net/mac80211/cfg.c
> +++ b/net/mac80211/cfg.c
> @@ -1754,6 +1754,15 @@ static int sta_link_apply_parameters(struct ieee80211_local *local,
>  						    params->eht_capa_len,
>  						    link_sta);
>  
> +	/* update nss if not done already for the link sta,
> +	 * for the deflink the nss will be updated once the
> +	 * assoc flag is set through set station. For the
> +	 * non-deflink sta we would reach here only during assoc,
> +	 * so we would have all caps to calculate the nss.
> +	 */
> +	if (&sta->deflink != link_sta)

NACK on that check. Please find a better place, or change the existing
code as well, or something.

johannes


  reply	other threads:[~2023-02-14 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 22:12 [PATCH v2] wifi: mac80211: update rx nss for the link sta Sriram R
2023-02-14 12:48 ` Johannes Berg [this message]
2023-02-14 16:36   ` Sriram R (QUIC)

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=16d922bd32b30e1a4282dc5941c6fff3b23908ca.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_srirrama@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 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).