ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Félix Sipma" <felix+kernel@gueux.org>
To: ath10k@lists.infradead.org
Subject: [PATCH] Revert "ath: add support for special 0x0 regulatory domain"
Date: Thu, 22 Oct 2020 19:21:13 +0200	[thread overview]
Message-ID: <20201022172113.GA1367233@capeo.gueux.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 486 bytes --]

Hello,

Sorry if I break the thread, I'm not subscribed and do not have access 
to the message-id.

I noticed the last message about this issue was on August:
https://lists.infradead.org/pipermail/ath10k/2020-August/011785.html

I got caught by this bug, too. I use a Compex wle900vx (qca988x).

Is there something preventing 
https://patchwork.kernel.org/project/ath10k/patch/20200527165718.129307-1-briannorris@chromium.org/
from being merged?

Regards,

-- 
Félix

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

             reply	other threads:[~2020-10-22 17:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 17:21 Félix Sipma [this message]
     [not found] ` <CANe27jKpYm29QOjYOZ_jwHiRxuWx66J+th8-zgbXK4geiCU0_Q@mail.gmail.com>
2020-10-29 14:06   ` [PATCH] Revert "ath: add support for special 0x0 regulatory domain" Félix Sipma
2020-10-30  7:20     ` Jouni Malinen
2020-10-30  8:51       ` Félix Sipma
2020-12-20  1:32         ` Julian Phillips
2020-10-30 13:23       ` Alvin Sipraga
2020-12-21 13:43         ` sparks71
  -- strict thread matches above, loose matches on Subject: below --
2020-12-21 12:15 sparks71
2020-07-30 12:49 Alvin Šipraga
2020-08-27  7:59 ` Alvin Šipraga
2020-08-27 10:12   ` Kalle Valo
2020-08-27 10:25     ` Alvin Šipraga
2020-05-27 16:57 Brian Norris
2020-05-28 12:02 ` Julian Calaby
     [not found]   ` <CAJ-Vmomx0UFEa1w2HsGMQsZb+K8hyK=Zz9cKSo7tHv5GiMc1yw@mail.gmail.com>
2020-06-02 18:35     ` Brian Norris
2022-03-07 17:45 ` Kalle Valo
2022-04-23 10:52 ` Patrick Steinhardt
2022-04-25 18:54   ` Brian Norris
2022-05-09 18:16     ` Cale Collins
2022-05-11 22:52       ` Cale Collins
2022-08-30 21:56         ` Brian Norris
2022-09-19 17:24           ` Tim Harvey
2022-09-19 23:42             ` Sergey Ryazanov
2022-09-20  5:42               ` Sebastian Gottschall

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=20201022172113.GA1367233@capeo.gueux.org \
    --to=felix+kernel@gueux.org \
    --cc=ath10k@lists.infradead.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).