mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "François Roux" <franzelfranzel@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Diederik de Haas <diederik@cknow-tech.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: nl80211: don't WARN on a missing self-managed regdom
Date: Sun, 11 Oct 2026 09:49:28 +0200	[thread overview]
Message-ID: <20261011074928.9381-1-franzelfranzel@gmail.com> (raw)
In-Reply-To: <16aa99921c4e92e8d4da3c84aacbec2e673666aa.camel@sipsolutions.net>

On Wed, 2026-10-07 at 16:55 +0200, Johannes Berg wrote:
> I'm not a fan of this, I think the drivers should have the regdom ready.
[...]
> Anyway I think we need to fix the bugs, not paper over them.

Fair enough, please drop this patch.

I've sent an ath12k fix that applies the boot-time regdomain before
ieee80211_register_hw():

https://lore.kernel.org/all/20261011074433.9187-1-franzelfranzel@gmail.com/

wiphy_register() holds the RTNL until wiphy_regulatory_register() has
applied it, and nl80211_get_reg_do() takes the RTNL too, so the window
is gone. On the Surface Pro 11 the warning no longer shows up over boots
and repeated driver unbind/bind, where it used to on every rebind.

Diederik, thanks a lot for testing. As Johannes said, your BE200 needs
the iwlwifi side fixed instead.

François

      parent reply	other threads:[~2026-10-11  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 16:17 François Roux
2026-10-07 12:33 ` Diederik de Haas
2026-10-07 14:55 ` Johannes Berg
2026-10-07 15:18   ` Diederik de Haas
2026-10-07 15:20     ` Johannes Berg
2026-10-11  7:49   ` François Roux [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=20261011074928.9381-1-franzelfranzel@gmail.com \
    --to=franzelfranzel@gmail.com \
    --cc=diederik@cknow-tech.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®