From: Nathan Chancellor <nathan@kernel.org>
To: Finn Behrens <me@kloenk.dev>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v5] nl80211: reset regdom when reloading regdb
Date: Tue, 30 Nov 2021 09:02:24 -0700 [thread overview]
Message-ID: <YaZLEEj2pUU/DhZD@archlinux-ax161> (raw)
In-Reply-To: <YaIIZfxHgqc/UTA7@gimli.kloenk.dev>
Hi Finn,
On Sat, Nov 27, 2021 at 11:28:53AM +0100, Finn Behrens wrote:
> this reloads the regdom when the regulatory db is reloaded.
> Without this patch the user had to change the regulatoy domain to a
> different, and then reset it to the one the user is in, to have the new
> regulatory db take effect
>
> Signed-off-by: Finn Behrens <fin@nyantec.com>
This patch as commit 1eda919126b4 ("nl80211: reset regdom when reloading
regdb") in -next causes the following clang warning/error:
net/wireless/reg.c:1137:23: error: implicit conversion from enumeration type 'enum nl80211_user_reg_hint_type' to different enumeration type 'enum nl80211_reg_initiator' [-Werror,-Wenum-conversion]
request->initiator = NL80211_USER_REG_HINT_USER;
~ ^~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
Should that be NL80211_REGDOM_SET_BY_CORE (same value, 0) or something
different?
Cheers,
Nathan
next prev parent reply other threads:[~2021-11-30 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 12:45 [PATCH] nl80211: reset regdom when reloading regdb Finn Behrens
2020-11-26 10:39 ` [PATCH v2] " Finn Behrens
2020-11-26 12:58 ` kernel test robot
2020-11-26 12:58 ` kernel test robot
2020-12-04 11:39 ` Johannes Berg
2021-11-13 10:54 ` [PATCH v4] " Finn Behrens
2021-11-26 12:08 ` Johannes Berg
2021-11-27 10:28 ` [PATCH v5] " Finn Behrens
2021-11-30 16:02 ` Nathan Chancellor [this message]
2021-11-30 16:50 ` Finn Behrens
2021-11-30 18:32 ` Nathan Chancellor
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=YaZLEEj2pUU/DhZD@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=me@kloenk.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.