ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Kouroche Bouchiat <kouroche.bouchiat@gmail.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k firmware-6.bin bug: Disconnections every 20 minutes on QCA6174
Date: Thu, 17 Aug 2017 16:03:55 +0000	[thread overview]
Message-ID: <87valm2nbp.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAJ-Vmo=wzZn10wu74r54N+SC-dY7tq1P6EghPLgHp6A326gUoA@mail.gmail.com>	(Adrian Chadd's message of "Thu, 17 Aug 2017 08:54:15 -0700")

Adrian Chadd <adrian@freebsd.org> writes:

> I'd rather see the ones that are known-to-be-ok-to-ignore be ignored.

Absolutely and that's what I meant. But I think there was a discussion
before that I least one event was ok to ignore (I have forgotten the
details already).

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

      reply	other threads:[~2017-08-17 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06 22:10 ath10k firmware-6.bin bug: Disconnections every 20 minutes on QCA6174 Kouroche Bouchiat
2017-08-16 14:14 ` Kalle Valo
2017-08-16 14:24   ` Gilbert Moisio
2017-08-16 14:42     ` Kalle Valo
2017-08-16 15:13       ` Gilbert Moisio
2017-08-16 16:26         ` Kalle Valo
     [not found]           ` <CAM8JFhCpWBDv=_rZ_KDTsQ008wjUgv5nix=kxv-RPd2035xGLQ@mail.gmail.com>
2017-08-17  7:11             ` Kalle Valo
     [not found]             ` <CAPYrjBUrEuuxpO=KYi1EXh-bZU2sPNLEsnNZnnp6_w1viss3wQ@mail.gmail.com>
2017-08-17  7:14               ` Kalle Valo
2017-08-17  8:59                 ` Kouroche Bouchiat
2017-08-17 13:56                   ` Kalle Valo
2017-08-17 15:54                     ` Adrian Chadd
2017-08-17 16:03                       ` Kalle Valo [this message]

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=87valm2nbp.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=kouroche.bouchiat@gmail.com \
    /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