All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leon M. George" <leon@georgemail.eu>
To: ath10k@lists.infradead.org
Subject: Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
Date: Wed, 22 Jul 2020 18:04:42 +0200	[thread overview]
Message-ID: <20200722180442.03b40f01@brot> (raw)
In-Reply-To: <cdba7890-62e4-4d99-bd0f-f1d458a4adc7@candelatech.com>

Hi Ben,

I was unclear in my last email.
Re-phrasing from my openwrt forum post:

I've tested various combinations of openwrt-trunk (now and early March) / 19.07, ath10k stock / ct driver, and stock / ct firmware.

regards,
Leon


On Wed, 22 Jul 2020 07:27:16 -0700
Ben Greear <greearb@candelatech.com> wrote:

> On 7/22/20 7:18 AM, Leon M. George wrote:
> > Hi :-)
> > 
> > I've encountered connection issues that appear to be strongly
> > related to the problem in this thread [1] (found via the arch linux
> > bug tracker [2]).
> 
> If this is ath10k-ct only problem, plz don't bother this list and
> send to just me and/or add to ath10k-ct bugtracker on github.
> 
> If it does affect upstream ath10k too, then that would be valid for
> this mailing list.
> 
> Thanks,
> Ben
> 

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

  reply	other threads:[~2020-07-22 16:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 14:18 duplicate authentications / excessive missing ACKs / deauth due to inactivity timer Leon M. George
2020-07-22 14:27 ` Ben Greear
2020-07-22 16:04   ` Leon M. George [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-01 16:30 Justin Capella
2019-12-01 17:01 ` Adrian Chadd
2019-12-01 17:18   ` Justin Capella
2019-12-01 17:21     ` Adrian Chadd
2019-12-01 18:53       ` Justin Capella

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=20200722180442.03b40f01@brot \
    --to=leon@georgemail.eu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.