All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	 James Prestwood <prestwoj@gmail.com>,
	 <linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>,
	 LKML <linux-kernel@vger.kernel.org>,
	 Chun Wu <chunwu@qti.qualcomm.com>
Subject: Re: invalid vht params rate 1920 100kbps nss 2 mcs 9
Date: Mon, 08 Jul 2024 13:33:08 +0300	[thread overview]
Message-ID: <87sewkcgwr.fsf@kernel.org> (raw)
In-Reply-To: <ceddb62b-61dd-44c9-babd-cd375c5a147d@quicinc.com> (Baochen Qiang's message of "Fri, 5 Jul 2024 18:51:47 +0800")

Baochen Qiang <quic_bqiang@quicinc.com> writes:

>>>> 2.  invalid vht params rate 960 100kbps nss 1 mcs 9
>>>> 3.  invalid vht params rate 1730 100kbps nss 2 mcs 9
>>>> 4.  invalid vht params rate 1920 100kbps nss 2 mcs 9
>>>
>>> OK, these are due to mismatch between host and QCA6174 firmware, we
>>> can update host to fix them.
>
> Kalle, the root cause to these three warnings are clear now and if you
> agree I can submit patches to fix them. Or I can also wait until the
> NSS 3 issue is clear.

I'm not sure why would we want to wait for the NSS 3 to be solved? Based
on my (limited) understanding I think it would be good to submit patches
for solved issues now.

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

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


  parent reply	other threads:[~2024-07-08 10:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 13:10 invalid vht params rate 1920 100kbps nss 2 mcs 9 Paul Menzel
2024-06-17 15:09 ` James Prestwood
2024-06-17 15:27   ` Kalle Valo
2024-06-17 15:40     ` James Prestwood
2024-06-18 10:33       ` Kalle Valo
2024-06-18 10:48         ` Baochen Qiang
2024-06-26  8:53         ` Baochen Qiang
2024-06-26  9:12           ` Paul Menzel
2024-06-26 10:16             ` Kalle Valo
2024-06-26 11:48               ` Paul Menzel
2024-06-26 12:34                 ` Kalle Valo
2024-07-05  2:47             ` Baochen Qiang
2024-07-05  6:55               ` Paul Menzel
2024-07-05 10:51                 ` Baochen Qiang
2024-07-05 11:52                   ` Paul Menzel
2024-07-08  1:53                     ` Baochen Qiang
2024-07-08 10:36                       ` Kalle Valo
2024-07-08 10:33                   ` Kalle Valo [this message]
2024-07-09  1:33                     ` Baochen Qiang
2024-06-27 17:42           ` James Prestwood
2024-06-27 18:25             ` Kalle Valo
2024-06-28  1:25               ` Baochen Qiang

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=87sewkcgwr.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=chunwu@qti.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=prestwoj@gmail.com \
    --cc=quic_bqiang@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 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.