All of lore.kernel.org
 help / color / mirror / Atom feed
From: timur.kristof@gmail.com
To: Ryan Hsu <ryanhsu@codeaurora.org>, Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org
Subject: Re: Frequent ath10k crashes with QCA6174 on kernels 4.16 and 4.17
Date: Fri, 08 Jun 2018 21:27:56 +0200	[thread overview]
Message-ID: <1528486076.3619.2.camel@gmail.com> (raw)
In-Reply-To: <89a29eb6-996e-1c8e-b332-c14fdf241b79@codeaurora.org>

On Fri, 2018-06-08 at 11:37 -0700, Ryan Hsu wrote:
> On 05/30/2018 12:15 AM, Timur Kristóf wrote:
> 
> > On Tue, 2018-05-29 at 22:36 +0300, Timur Kristóf wrote:
> > > 
> > > Thanks!
> > > It does not apply to 4.17-rc6 as-is, either, but it seems fixable
> > > at
> > > the first glance.
> > > 
> > 
> > Basically, the author forgot to define WMI_PEER_PHYMODE but some
> > searching found another QCA driver where it is 0xd so I decided to
> > go
> > with that. The other error was trivial.
> > 
> > I fixed the patch and applied locally on top of 4.17-rc7. Currently
> > running it to test if it really mitigates the issue. Will report
> > back
> > when I have results, and submit the patch if I'm satisfied.
> > 
> 
> Sorry, I've been dragged by something else and didn't update this
> promptly.
> I just sent the v2 including the missing WMI_PEER_PHYMODE.
> 
> Can you pick up the v2 and see if that help your issue?
> 
> https://patchwork.kernel.org/patch/10454967/
> 

Hi Ryan,

I already posted a patch v2 here:
http://lists.infradead.org/pipermail/ath10k/2018-May/011545.html
(Basically made the same changes as you.)
Yes, it fixes the problem.

Best regards,
Tim


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

  reply	other threads:[~2018-06-08 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29  8:52 Frequent ath10k crashes with QCA6174 on kernels 4.16 and 4.17 Timur Kristóf
2018-05-29 10:21 ` Kalle Valo
2018-05-29 12:32   ` Timur Kristóf
2018-05-29 13:29     ` Kalle Valo
2018-05-29 19:36       ` Timur Kristóf
2018-05-30  7:15         ` Timur Kristóf
2018-06-08 18:37           ` Ryan Hsu
2018-06-08 19:27             ` timur.kristof [this message]
2018-06-08 20:25               ` Ryan Hsu
2018-06-09 12:56                 ` Timur Kristóf

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=1528486076.3619.2.camel@gmail.com \
    --to=timur.kristof@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@codeaurora.org \
    --cc=ryanhsu@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 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.