Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <YSJ//ki/A1EgfLga@skv.local> <CA+ASDXNzv6D1PthjUU-CVw6amT+JHmJP2mNSL=LVJKGm0zkEXw@mail.gmail.com>
 <YSQC32TygIq2SHJR@skv.local> <CA+ASDXPi0RRd0gFYcON=XLu8ABwKKcRXf0j0QoCRnvDwGa0VyQ@mail.gmail.com>
 <4c44fdc2-8dde-8a98-8dd4-4b7e6b57a090@bang-olufsen.dk>
In-Reply-To: <4c44fdc2-8dde-8a98-8dd4-4b7e6b57a090@bang-olufsen.dk>
From:   Brian Norris <briannorris@chromium.org>
Date:   Tue, 29 Mar 2022 14:06:40 -0700
Message-ID: <CA+ASDXOeC+S2d7g0b=aS_q9XxNtdayF1S5XE9T85NZrxXnK5KA@mail.gmail.com>
Subject: Re: Revert: ath: add support for special 0x0 regulatory domain
To:     =?UTF-8?Q?Alvin_=C5=A0ipraga?= <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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Aug 24, 2021 at 1:00 AM Alvin =C5=A0ipraga <ALSI@bang-olufsen.dk> w=
rote:
> Numerous people - myself included - have cited sources clearly
> indicating that 0x0 =3D 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