From: Kalle Valo <kvalo@kernel.org>
To: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] ath11k: Enable threaded NAPI on WCN6750
Date: Thu, 08 Sep 2022 09:49:56 +0300 [thread overview]
Message-ID: <874jxicqcr.fsf@kernel.org> (raw)
In-Reply-To: <dcc14883-51c9-c1bb-bbea-1b309eccedf2@quicinc.com> (Manikanta Pubbisetty's message of "Fri, 2 Sep 2022 18:47:41 +0530")
Manikanta Pubbisetty <quic_mpubbise@quicinc.com> writes:
>> Also more testing would be nice. Enabling something like this with
>> testing only on one hardware family (WCN7850) can be risky. I always get
>> warm fuzzy feelings if a patch is tested with all three hardware
>> families we currently support:
>>
>> * IPQ8074 etc
>> * QCA6390 etc
>> * WCN7850
>
> WCN7850 should be an ath12k device If I'm correct.
Sorry, I meant WCN6855. Too many drivers and too many hardware...
> Regardless of the chip family, even I feel that the tput changes like
> these should be tested on all the chipsets. Availability of the
> hardware and time are something which are stopping me in testing the
> changes on all supported targets.
I have the same problem, I cannot test all possible hardware. That's why
I was requsting help here.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-09-08 6:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 13:51 [PATCH 0/3] Throughput fixes for WCN6750 Manikanta Pubbisetty
2022-07-20 13:51 ` [PATCH 1/3] ath11k: Enable threaded NAPI on WCN6750 Manikanta Pubbisetty
2022-09-02 12:37 ` Kalle Valo
2022-09-02 12:54 ` Manikanta Pubbisetty
2022-09-02 12:48 ` Kalle Valo
2022-09-02 13:17 ` Manikanta Pubbisetty
2022-09-02 13:20 ` Robert Marko
2022-09-02 13:42 ` Manikanta Pubbisetty
2022-09-02 13:46 ` Robert Marko
2022-09-02 14:30 ` Manikanta Pubbisetty
2022-09-08 6:46 ` Kalle Valo
2022-09-08 8:49 ` Robert Marko
2022-09-08 12:15 ` Kalle Valo
2022-09-08 6:49 ` Kalle Valo [this message]
2022-07-20 13:51 ` [PATCH 2/3] ath11k: Add multi TX ring support for WCN6750 Manikanta Pubbisetty
2022-09-02 12:49 ` Kalle Valo
2022-09-02 13:44 ` Manikanta Pubbisetty
2022-07-20 13:51 ` [PATCH 3/3] ath11k: Increase TCL data ring size " Manikanta Pubbisetty
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=874jxicqcr.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_mpubbise@quicinc.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;
as well as URLs for NNTP newsgroup(s).