From: Johannes Berg <johannes@sipsolutions.net>
To: Aditya Kumar Singh <quic_adisi@quicinc.com>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: [PATCH] wifi: mac80211: fix assigning channel in activate links
Date: Tue, 01 Oct 2024 08:31:12 +0200 [thread overview]
Message-ID: <0353d31db76afbd5d9bb2e7d42246ae3c8e14044.camel@sipsolutions.net> (raw)
In-Reply-To: <20241001041518.2236297-1-quic_adisi@quicinc.com>
> + /*
> + * inform about the link info changed parameters after all
> + * stations are also added
> + */
I don't understand that comment - you're not doing anything with the
stations here? And per the commit log it's explicitly _not_ after doing
the AP station. I'm not sure we should set up everything before the AP
station?
> + BSS_CHANGED_HE_BSS_COLOR);
> +
> + }
You make it look like you just moved code but also snuck in a new blank
line :)
johannes
> +
> for_each_set_bit(link_id, &rem, IEEE80211_MLD_MAX_NUM_LINKS) {
> struct ieee80211_link_data *link;
I also think you put this code too early now - you're now first using
more channel contexts by way of _ieee80211_link_use_channel() before you
even release the ones from deactivated ("rem" bitmap in this code)
links. That doesn't seem like it could work correctly in general.
johannes
next prev parent reply other threads:[~2024-10-01 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 4:15 [PATCH] wifi: mac80211: fix assigning channel in activate links Aditya Kumar Singh
2024-10-01 6:31 ` Johannes Berg [this message]
2024-10-01 7:17 ` Aditya Kumar Singh
2024-10-01 7:22 ` Johannes Berg
2024-10-01 7:37 ` Aditya Kumar Singh
2024-10-01 8:08 ` Johannes Berg
2024-10-01 8:26 ` Aditya Kumar Singh
2024-10-01 8:28 ` Johannes Berg
2024-10-01 9:16 ` Aditya Kumar Singh
2024-10-01 6:32 ` Johannes Berg
2024-10-01 7:20 ` Aditya Kumar Singh
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=0353d31db76afbd5d9bb2e7d42246ae3c8e14044.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_adisi@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