public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>, Zenm Chen <zenmchen@gmail.com>
Subject: RE: [PATCH v3] wifi: rtl8xxxu: Fix LED control code of RTL8192FU
Date: Tue, 2 Jan 2024 01:50:00 +0000	[thread overview]
Message-ID: <2c67bbe4a3c84b45acb74b2e945eb2a8@realtek.com> (raw)
In-Reply-To: <7a2c3158-3a45-4466-b11e-fc09802b20e2@gmail.com>



> -----Original Message-----
> From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Sent: Sunday, December 31, 2023 6:46 AM
> To: linux-wireless@vger.kernel.org
> Cc: Jes Sorensen <Jes.Sorensen@gmail.com>; Ping-Ke Shih <pkshih@realtek.com>; Zenm Chen
> <zenmchen@gmail.com>
> Subject: [PATCH v3] wifi: rtl8xxxu: Fix LED control code of RTL8192FU
> 
> Some devices, like the Comfast CF-826F, use LED1, which already works.
> Others, like Asus USB-N13 C1, use LED0, which doesn't work correctly.
> 
> Write the right values to the LED control registers to make LED0 work
> as well.
> 
> This is unfortunately tested only with the Comfast CF-826F.
> 
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>

Thank you and Zenm for this work! 

Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>



  parent reply	other threads:[~2024-01-02  1:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 22:45 [PATCH v3] wifi: rtl8xxxu: Fix LED control code of RTL8192FU Bitterblue Smith
2024-01-01  5:13 ` Zenm Chen
2024-01-02  1:50 ` Ping-Ke Shih [this message]
2024-01-10 14:55 ` 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=2c67bbe4a3c84b45acb74b2e945eb2a8@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=zenmchen@gmail.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