ath11k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: alan <alan@abraxas.to>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k/mhi backtraces on shutdown with linux-next
Date: Wed, 16 Dec 2020 20:39:19 +0200	[thread overview]
Message-ID: <87tuslvbmw.fsf@codeaurora.org> (raw)
In-Reply-To: <01AD5E2A-6A3A-4F67-B050-70859285A4C0@abraxas.to> (alan@abraxas.to's message of "Sun, 13 Dec 2020 14:22:48 -0500")

alan <alan@abraxas.to> writes:

> I want to thank you for your work on ath11k. I just bought a Dell XPS
> 13 9310 with the AX500 wireless chip and was disappointed to discover
> it didn’t work with linux.
>
> I have been following the ath11k mailing list and it appears that you
> are getting close to a solution - that observation about the M2 state
> in the MHI looks very promising.

Indeed, it seems we have a functional workaround now. I hope you saw
this:

https://lore.kernel.org/ath11k/87blew3e4q.fsf@codeaurora.org/

I have received multiple positive reports with tag.

> PS. I visited Tampere once, in 1995. I gave a talk at the Scandic
> Rosendahl in Pyynikki. Beautiful place!

I bet it wasn't this time of year, now it's so dark and muddy ;) Hoping
for the snow to come soon, then it will be better.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

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

  reply	other threads:[~2020-12-16 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-13 19:22 Re: ath11k/mhi backtraces on shutdown with linux-next alan
2020-12-16 18:39 ` Kalle Valo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-12  1:23 Dmitry Baryshkov
2020-12-12  5:11 ` Kalle Valo
2020-12-12 21:04   ` Dmitry Baryshkov
2020-12-16 18:34     ` Kalle Valo
2021-10-07  9:27       ` Kalle Valo

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=87tuslvbmw.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=alan@abraxas.to \
    --cc=ath11k@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).