ath11k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Procopiuc <pavel.procopiuc@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: PROBLEM: unable to get QCA6390 to work
Date: Tue, 3 Nov 2020 22:01:46 +0100	[thread overview]
Message-ID: <f99862f4-9b3a-03e5-cd26-1de6136f9e46@gmail.com> (raw)
In-Reply-To: <87ft5qsem9.fsf@codeaurora.org>

Thanks! fd5ad4d1e980 works fine and 3650b228f83a is broken. I'm doing the bisecting, but it looks like it will take some 
time.

Op 03.11.2020 om 15:23 schreef Kalle Valo:
> For me v5.10-rc2 (no extra patches) was working fine. A bisection would
> be a good next step. What I suggest that is that you first test these
> three commits from Linus' tree in this order:
> 
> fd5ad4d1e980 wcn36xx: Advertise beacon filtering support in bmps
> 3650b228f83a Linux 5.10-rc1
> 3cea11cd5e3b Linux 5.10-rc2
> 
> Commit fd5ad4d1e980 is based on v5.9-rc6 so try that first. In these
> three commits ath11k is practically identical, the only change is a
> small bugfix in commit 8431350eee2e ("ath11k: Fix memory leak on error
> path").

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2020-11-03 21:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 10:32 PROBLEM: unable to get QCA6390 to work Pavel Procopiuc
2020-11-02 17:42 ` Kalle Valo
2020-11-02 18:21   ` Pavel Procopiuc
2020-11-02 21:14     ` Pavel Procopiuc
2020-11-03  6:56       ` Kalle Valo
2020-11-03 13:12         ` Pavel Procopiuc
2020-11-04  9:32           ` Pavel Procopiuc
2020-11-03 14:23         ` Kalle Valo
2020-11-03 21:01           ` Pavel Procopiuc [this message]
2020-11-04  9:12             ` Kalle Valo
2020-11-04 22:15               ` Pavel Procopiuc
2020-11-05  9:04                 ` Regression: QCA6390 fails with "mm/page_alloc: place pages to tail in __free_pages_core()" Kalle Valo
2020-11-05  9:47                   ` Pavel Procopiuc
2020-11-05 10:42                   ` Vlastimil Babka
2020-11-05 10:45                     ` Pavel Procopiuc
2020-11-05 11:13                     ` David Hildenbrand
2020-11-05 12:55                       ` Pavel Procopiuc
2020-11-05 20:23                         ` David Hildenbrand
2020-11-06 17:32                           ` Pavel Procopiuc
2020-11-06 20:41                             ` David Hildenbrand
2020-11-11 19:23                       ` Kalle Valo
2020-11-11 20:41                         ` Pavel Procopiuc
2020-11-12 10:48                           ` David Hildenbrand
2020-11-13  8:17                             ` Pavel Procopiuc
2020-11-13 11:08                               ` Carl Huang
2020-11-13 11:44                                 ` Carl Huang
2020-11-13 12:52                                 ` Pavel Procopiuc
2020-11-13 13:36                                   ` wi nk
2020-11-13 13:56                                     ` David Hildenbrand
2020-11-13 15:49                                       ` wi nk
2020-11-03  8:42       ` PROBLEM: unable to get QCA6390 to work Carl Huang
2020-11-03 14:12         ` Pavel Procopiuc

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=f99862f4-9b3a-03e5-cd26-1de6136f9e46@gmail.com \
    --to=pavel.procopiuc@gmail.com \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@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).