From: Brian Norris <briannorris@chromium.org>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: Andrey Skvortsov <andrej.skvortzov@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>,
Wen Gong <wgong@codeaurora.org>,
Julian Calaby <julian.calaby@gmail.com>, svp <svpm@yandex.ru>,
"felix+debian@gueux.org" <felix+debian@gueux.org>,
Massimo Maggi <me@massimo-maggi.eu>
Subject: Re: Revert: ath: add support for special 0x0 regulatory domain
Date: Tue, 29 Mar 2022 14:06:40 -0700 [thread overview]
Message-ID: <CA+ASDXOeC+S2d7g0b=aS_q9XxNtdayF1S5XE9T85NZrxXnK5KA@mail.gmail.com> (raw)
In-Reply-To: <4c44fdc2-8dde-8a98-8dd4-4b7e6b57a090@bang-olufsen.dk>
On Tue, Aug 24, 2021 at 1:00 AM Alvin Šipraga <ALSI@bang-olufsen.dk> wrote:
> Numerous people - myself included - have cited sources clearly
> indicating that 0x0 = US, NOT unset. See the same post[1] for more info.
>
> I still think this patch should be reverted unless somebody can provide
> a source to the contrary, re: the meaning of 0x0.
>
> It's unfortunate that this is still affecting users, particularly when
> the original author of the patch even asked for it to be reverted.[2]
FYI, my revert was recently merged to Linus's tree and is making its
way into various -stable trees:
https://git.kernel.org/linus/1ec7ed5163c70a0d040150d2279f932c7e7c143f
Side note: it's a small shame that Kalle's scripts seem to have munged
the authorship date -- git thinks it was authored in 2022, when in
fact it was in 2020 ;)
Regards,
Brian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2022-03-29 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 16:49 Revert: ath: add support for special 0x0 regulatory domain Andrey Skvortsov
2021-08-23 17:23 ` Brian Norris
2021-08-23 20:19 ` Andrey Skvortsov
2021-08-23 21:06 ` Brian Norris
2021-08-24 8:00 ` Alvin Šipraga
2022-03-29 21:06 ` Brian Norris [this message]
2022-03-29 21:21 ` Alvin Šipraga
2022-03-30 5:35 ` Kalle Valo
2021-08-23 18:15 ` Peter Oh
2021-08-23 20:39 ` Andrey Skvortsov
2021-09-01 22:37 Bryce Allen
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='CA+ASDXOeC+S2d7g0b=aS_q9XxNtdayF1S5XE9T85NZrxXnK5KA@mail.gmail.com' \
--to=briannorris@chromium.org \
--cc=ALSI@bang-olufsen.dk \
--cc=andrej.skvortzov@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=felix+debian@gueux.org \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@massimo-maggi.eu \
--cc=svpm@yandex.ru \
--cc=wgong@codeaurora.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).