From: Nicolas Schichan <nschichan@freebox.fr>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Linus Torvalds <torvalds@linuxfoundation.org>,
Wren Turkal <wt@penguintechs.org>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
regressions@lists.linux.dev,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Hemant Kumar <hemantk@codeaurora.org>,
Loic Poulain <loic.poulain@linaro.org>
Subject: Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310
Date: Mon, 30 Aug 2021 18:04:04 +0200 [thread overview]
Message-ID: <CAHNNwZD2dLC9dWui7kAEg8R04U0LVdQJMJCyugkHA6rdfRwGLQ@mail.gmail.com> (raw)
In-Reply-To: <87sfyv5abg.fsf@codeaurora.org>
On Fri, Aug 27, 2021 at 2:41 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> Jakub Kicinski <kuba@kernel.org> writes:
> > Done, thank you!
>
> Thank you waiting for me :)
>
> I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
> laptop with QCA6390 and ath11k works without problems. So the issue
> should be solved in the final v5.14 release.
>
Good evening,
I have tested loading ath11k on v5.14.0 and I can confirm that the
driver loads fine now, with a phy and wlan interface being created as
a result.
Thanks and best regards,
--
Nicolas Schichan
next prev parent reply other threads:[~2021-08-30 16:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a8cddf24-ecfc-088e-27f4-98cbbb5fb67c@penguintechs.org>
2021-08-23 12:53 ` 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310 Kalle Valo
2021-08-23 16:02 ` Nicolas Schichan
2021-08-23 17:40 ` Kalle Valo
2021-08-26 14:25 ` [regression] " Kalle Valo
2021-08-26 14:38 ` Greg Kroah-Hartman
2021-08-26 14:48 ` Jakub Kicinski
2021-08-26 15:00 ` Kalle Valo
2021-08-26 17:33 ` Kalle Valo
2021-08-26 18:12 ` Jakub Kicinski
2021-08-27 12:41 ` Kalle Valo
2021-08-30 16:04 ` Nicolas Schichan [this message]
2021-08-31 10:37 ` Kalle Valo
2021-08-27 12:46 ` Kalle Valo
2021-08-23 16:17 ` Wren Turkal
2021-08-27 12:43 ` 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=CAHNNwZD2dLC9dWui7kAEg8R04U0LVdQJMJCyugkHA6rdfRwGLQ@mail.gmail.com \
--to=nschichan@freebox.fr \
--cc=ath11k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linuxfoundation.org \
--cc=wt@penguintechs.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).