From: Kalle Valo <kvalo@kernel.org>
To: Tanguy Serrat <tanguy@squaremind.io>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: QCN9074: low HE-MCS index
Date: Tue, 11 Jul 2023 11:39:48 +0300 [thread overview]
Message-ID: <87jzv696zv.fsf@kernel.org> (raw)
In-Reply-To: <CAPr+0HbwpA0KrV71ah8bQ_Gnn9Ch2PMZnHE3uqRUrNU8=DoMFA@mail.gmail.com> (Tanguy Serrat's message of "Tue, 11 Jul 2023 10:15:50 +0200")
Tanguy Serrat <tanguy@squaremind.io> writes:
> Dear Kalle,
>
> Thank you for your reply.
>
> I have opened two separate issues:
> 1) https://bugzilla.kernel.org/show_bug.cgi?id=217536 - related to a
> previous issue I encountered.
>
> 2) https://bugzilla.kernel.org/show_bug.cgi?id=217652 - related to this feed.
>
> I have tested 3m apart, as described in 217652, results are just
> slightly better in terms of reported MCS. I still seem to be missing
> all capabilities over 7. I have attached the full dmesg log and
> .config file to the bug report
Thanks for filing the report, we will look at bug #217652 and get back
to you. But do note that this will most likely take some time, our
backlog is long and people are also taking vacations. I just came back
yesterday and I'm hoping to take more vacation later this month.
--
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
next prev parent reply other threads:[~2023-07-11 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 12:27 ath11k: QCN9074: low HE-MCS index Tanguy Serrat
2023-06-26 13:50 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-10 11:01 ` Tanguy Serrat
2023-07-10 11:54 ` Thorsten Leemhuis
2023-07-11 6:49 ` Kalle Valo
2023-07-11 8:15 ` Tanguy Serrat
2023-07-11 8:39 ` Kalle Valo [this message]
2023-07-12 8:37 ` Tanguy Serrat
2023-09-26 11:05 ` Tanguy Serrat
2023-09-27 7:16 ` 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=87jzv696zv.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=tanguy@squaremind.io \
/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