public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: stable@vger.kernel.org,
	Miri Korenblit <miriam.rachel.korenblit@intel.com>
Subject: Re: [PATCH 4.19] cfg80211: set custom regdomain after wiphy registration
Date: Fri, 27 May 2022 18:08:51 +0200	[thread overview]
Message-ID: <YpD3k0yXx6d7So7W@kroah.com> (raw)
In-Reply-To: <20220527091151.45581-1-johannes@sipsolutions.net>

On Fri, May 27, 2022 at 11:11:51AM +0200, Johannes Berg wrote:
> From: Miri Korenblit <miriam.rachel.korenblit@intel.com>
> 
> commit 1b7b3ac8ff3317cdcf07a1c413de9bdb68019c2b upstream.
> 
> We used to set regulatory info before the registration of
> the device and then the regulatory info didn't get set, because
> the device isn't registered so there isn't a device to set the
> regulatory info for. So set the regulatory info after the device
> registration.
> Call reg_process_self_managed_hints() once again after the device
> registration because it does nothing before it.
> 
> Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
> Link: https://lore.kernel.org/r/iwlwifi.20210618133832.c96eadcffe80.I86799c2c866b5610b4cf91115c21d8ceb525c5aa@changeid
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
>  net/wireless/core.c | 7 ++++---
>  net/wireless/reg.c  | 1 +
>  2 files changed, 5 insertions(+), 3 deletions(-)

What about versions for 5.4.y and 5.10.y as well?  We can't just fix an
issue in an older kernel tree and ignore it in newer ones, right?

thanks,

greg k-h

  reply	other threads:[~2022-05-27 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  9:11 [PATCH 4.19] cfg80211: set custom regdomain after wiphy registration Johannes Berg
2022-05-27 16:08 ` Greg KH [this message]
2022-05-27 16:17   ` Johannes Berg
2022-06-03 13:35     ` Greg KH

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=YpD3k0yXx6d7So7W@kroah.com \
    --to=greg@kroah.com \
    --cc=johannes@sipsolutions.net \
    --cc=miriam.rachel.korenblit@intel.com \
    --cc=stable@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