From: Johannes Berg <johannes@sipsolutions.net>
To: "Hodaszi, Robert" <Robert.Hodaszi@digi.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] Revert "cfg80211: fix processing world regdomain when non modular"
Date: Fri, 14 Jun 2019 16:01:00 +0200 [thread overview]
Message-ID: <6a9c7642a2fcca60658036c605438ff2ac982bd0.camel@sipsolutions.net> (raw)
In-Reply-To: <32951d52-3f9d-aaee-fa07-75585c03edba@digi.com>
On Fri, 2019-06-14 at 13:58 +0000, Hodaszi, Robert wrote:
>
> I didn't just resend that. I just realized, accidentally I forgot to fix
> the debug message printing function, that define doesn't exist anymore.
> Sorry for the confusion!
Oops. I looked too superficially then and didn't even see the
difference, sorry.
I guess that's why Kalle always says you should have a patch changelog
:-)
> Under "original issue", you mean the issue, which commit
> 96cce12ff6e0bc9d9fcb2235e08b7fc150f96fd2 (cfg80211: fix processing world
> regdomain when non modular) supposed to fix?
Yes.
> That still won't work, but
> that didn't work neither before I reverted the patch, because crda call
> timeout will just drop the last packet. Also, as it re-processed the
> last request, not just resent it, it caused undesired states. Like when
> I used 2 WiFi modules with US regulatory domains, after enumeration, my
> global regulator domain was set to "Country 98".
>
> To fix my issue, why I reverted the patch, and also fix the issue the
> reverted commit supposed to fix, I could imagine something like this.
> But I'm not sure, it doesn't have any side effect:
[snip]
Ok, thanks. I guess I'll have to look at this in more detail.
You don't happen to have a way to reproduce either issue with a hwsim
test case?
johannes
next prev parent reply other threads:[~2019-06-14 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 13:16 [PATCH v2] Revert "cfg80211: fix processing world regdomain when non modular" Hodaszi, Robert
2019-06-14 13:30 ` Johannes Berg
2019-06-14 13:58 ` Hodaszi, Robert
2019-06-14 14:01 ` Johannes Berg [this message]
2019-06-14 14:06 ` Hodaszi, Robert
2019-06-20 7:48 ` Kalle Valo
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=6a9c7642a2fcca60658036c605438ff2ac982bd0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Robert.Hodaszi@digi.com \
--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;
as well as URLs for NNTP newsgroup(s).