From: Johannes Berg <johannes@sipsolutions.net>
To: Aloka Dixit <alokad@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, John Crispin <john@phrozen.org>
Subject: Re: [PATCH v10 4/4] mac80211: CSA on non-transmitting interfaces
Date: Wed, 23 Jun 2021 18:03:09 +0200 [thread overview]
Message-ID: <1d8645c19faf4c7aa759d8af3d4dfd993049daf4.camel@sipsolutions.net> (raw)
In-Reply-To: <20210426190534.12667-5-alokad@codeaurora.org>
On Mon, 2021-04-26 at 12:05 -0700, Aloka Dixit wrote:
>
> + if (sdata->vif.mbssid.flags & IEEE80211_VIF_MBSSID_TX) {
> + struct ieee80211_sub_if_data *child;
> +
> + wiphy_unlock(sdata->local->hw.wiphy);
> + mutex_lock(&sdata->local->iflist_mtx);
> + list_for_each_entry(child, &sdata->local->interfaces, list)
> + if (child->vif.mbssid.parent == vif &&
> + ieee80211_sdata_running(child))
> + ieee80211_queue_work(&child->local->hw,
> + &child->csa_finalize_work);
> + mutex_unlock(&sdata->local->iflist_mtx);
> + wiphy_lock(sdata->local->hw.wiphy);
Same here wrt. locking, but for queueing work it shouldn't matter?
johannes
prev parent reply other threads:[~2021-06-23 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 19:05 [PATCH v10 0/4] multiple bssid and EMA support in AP mode Aloka Dixit
2021-04-26 19:05 ` [PATCH v10 1/4] nl80211: " Aloka Dixit
2021-06-14 16:15 ` Aloka Dixit
2021-06-23 15:55 ` Johannes Berg
2021-04-26 19:05 ` [PATCH v10 2/4] mac80211: multiple bssid support in interface handling Aloka Dixit
2021-06-23 15:57 ` Johannes Berg
2021-06-28 17:16 ` Aloka Dixit
2021-06-28 19:17 ` Johannes Berg
2021-04-26 19:05 ` [PATCH v10 3/4] mac80211: MBSSID and EMA support in beacon handling Aloka Dixit
2021-04-26 19:05 ` [PATCH v10 4/4] mac80211: CSA on non-transmitting interfaces Aloka Dixit
2021-06-23 16:03 ` Johannes Berg [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=1d8645c19faf4c7aa759d8af3d4dfd993049daf4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alokad@codeaurora.org \
--cc=john@phrozen.org \
--cc=linux-wireless@vger.kernel.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.