All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Chris Chiu <chris.chiu@canonical.com>
Cc: Jes.Sorensen@gmail.com, davem@davemloft.net, kuba@kernel.org,
	code@reto-schneider.ch, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chris Chiu <chris.chiu@canonical.com>
Subject: Re: [v3,2/2] rtl8xxxu: fill up txrate info for gen1 chips
Date: Wed,  6 Apr 2022 11:28:14 +0000 (UTC)	[thread overview]
Message-ID: <164924448932.19026.12333806311207815732.kvalo@kernel.org> (raw)
In-Reply-To: <20220325035735.4745-3-chris.chiu@canonical.com>

Chris Chiu <chris.chiu@canonical.com> wrote:

> RTL8188CUS/RTL8192CU(gen1) don't support rate adaptive report hence
> no real txrate info can be retrieved. The vendor driver reports the
> highest rate in HT capabilities from the IEs to avoid empty txrate.
> This commit initiates the txrate information with the highest supported
> rate negotiated with AP. The gen2 chip keeps update the txrate from
> the rate adaptive reports, and gen1 chips at least have non-NULL txrate
> after associated.
> 
> Signed-off-by: Chris Chiu <chris.chiu@canonical.com>

You ignored Reto's comment in v2 about misspelling of adaptive, but I'll fix
that during commit.

-- 
https://patchwork.kernel.org/project/linux-wireless/patch/20220325035735.4745-3-chris.chiu@canonical.com/

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


  reply	other threads:[~2022-04-06 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  3:57 [PATCH v3 0/2] rtl8xxxu: Fill up more TX information Chris Chiu
2022-03-25  3:57 ` [PATCH v3 1/2] rtl8xxxu: feed antenna information for cfg80211 Chris Chiu
2022-04-06 12:12   ` Kalle Valo
2022-03-25  3:57 ` [PATCH v3 2/2] rtl8xxxu: fill up txrate info for gen1 chips Chris Chiu
2022-04-06 11:28   ` Kalle Valo [this message]
2022-04-06  4:41 ` [PATCH v3 0/2] rtl8xxxu: Fill up more TX information Chris Chiu

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=164924448932.19026.12333806311207815732.kvalo@kernel.org \
    --to=kvalo@kernel.org \
    --cc=Jes.Sorensen@gmail.com \
    --cc=chris.chiu@canonical.com \
    --cc=code@reto-schneider.ch \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.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 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.