From: Brian Norris <briannorris@chromium.org>
To: Andrey Skvortsov <andrej.skvortzov@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>,
"Wen Gong" <wgong@codeaurora.org>,
"Kalle Valo" <kvalo@codeaurora.org>,
"Alvin Šipraga" <alsi@bang-olufsen.dk>,
"Julian Calaby" <julian.calaby@gmail.com>, svp <svpm@yandex.ru>,
felix+debian@gueux.org, "Massimo Maggi" <me@massimo-maggi.eu>
Subject: Re: Revert: ath: add support for special 0x0 regulatory domain
Date: Mon, 23 Aug 2021 10:23:35 -0700 [thread overview]
Message-ID: <CA+ASDXNzv6D1PthjUU-CVw6amT+JHmJP2mNSL=LVJKGm0zkEXw@mail.gmail.com> (raw)
In-Reply-To: <YSJ//ki/A1EgfLga@skv.local>
On Sun, Aug 22, 2021 at 9:49 AM Andrey Skvortsov
<andrej.skvortzov@gmail.com> wrote:
> 4) As many users are affected by this problem and maintainers don't really
> want to revert the problematic patch,
I'm not totally sure that's true. So far, it looks like an oversight.
Over a year ago, Kalle said he "just need[ed] to check something
internally first":
https://lore.kernel.org/linux-wireless/87r1rsbdnx.fsf@codeaurora.org/
I don't see the result of that, except that this is marked Superseded:
https://patchwork.kernel.org/project/linux-wireless/patch/20200730124923.271429-1-alsi@bang-olufsen.dk/
and this is marked Rejected:
https://patchwork.kernel.org/project/linux-wireless/patch/20200527165718.129307-1-briannorris@chromium.org/
I'm not sure if the Rejected was before or after the last reply above...
Maybe it needs an Nth person to submit a revert?
Brian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2021-08-23 17:24 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 [this message]
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
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+ASDXNzv6D1PthjUU-CVw6amT+JHmJP2mNSL=LVJKGm0zkEXw@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=kvalo@codeaurora.org \
--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).