From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH v2 3/8] wiphy: remove pending_freqs from wiphy_regdom_is_updating
Date: Fri, 16 Dec 2022 09:26:01 -0800 [thread overview]
Message-ID: <20221216172606.1799396-3-prestwoj@gmail.com> (raw)
In-Reply-To: <20221216172606.1799396-1-prestwoj@gmail.com>
We can determine this info based on the dump IDs.
---
src/wiphy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/wiphy.c b/src/wiphy.c
index 6b8f00a1..3777bd58 100644
--- a/src/wiphy.c
+++ b/src/wiphy.c
@@ -979,7 +979,7 @@ int wiphy_estimate_data_rate(struct wiphy *wiphy,
bool wiphy_regdom_is_updating(struct wiphy *wiphy)
{
- return wiphy->pending_freqs != NULL;
+ return wiphy->dump_id || (!wiphy->self_managed && wiphy_dump_id);
}
uint32_t wiphy_state_watch_add(struct wiphy *wiphy,
--
2.34.3
next prev parent reply other threads:[~2022-12-16 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 17:25 [PATCH v2 1/8] band: introduce new method of tracking frequencies James Prestwood
2022-12-16 17:26 ` [PATCH v2 2/8] wiphy: parse/store frequency info in band object James Prestwood
2022-12-16 17:26 ` James Prestwood [this message]
2022-12-16 17:26 ` [PATCH v2 4/8] wiphy: don't parse dumps from unregistered wiphy's James Prestwood
2022-12-16 17:26 ` [PATCH v2 5/8] wiphy: add getter for frequency/band info James Prestwood
2022-12-16 17:26 ` [PATCH v2 6/8] station: use wiphy_get_frequency_info James Prestwood
2022-12-16 17:26 ` [PATCH v2 7/8] ap: " James Prestwood
2022-12-16 17:26 ` [PATCH v2 8/8] wiphy: remove disabled_freqs and related dump code James Prestwood
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=20221216172606.1799396-3-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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.