From: Pkshih <pkshih@realtek.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
"kvalo@kernel.org" <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] rtw88: Fix missing support for Realtek 8821CE RFE Type 6
Date: Mon, 14 Mar 2022 00:21:45 +0000 [thread overview]
Message-ID: <9ae5780119e24142bffd855d915a5e92@realtek.com> (raw)
In-Reply-To: <20220313164358.30426-1-Larry.Finger@lwfinger.net>
> -----Original Message-----
> From: Larry Finger <Larry.Finger@lwfinger.net>
> Sent: Monday, March 14, 2022 12:44 AM
> To: kvalo@kernel.org
> Cc: linux-wireless@vger.kernel.org; Larry Finger <Larry.Finger@lwfinger.net>; Pkshih <pkshih@realtek.com>;
> stable@vger.kernel.org
> Subject: [PATCH] rtw88: Fix missing support for Realtek 8821CE RFE Type 6
>
> The rtl8821ce with RFE Type 6 behaves the same as ones with RFE Type 0.
>
> This change has been tested in the repo at git://GitHub.com/lwfinger/rtw88.git.
> It fixes commit 769a29ce2af4 ("rtw88: 8821c: add basic functions").
>
> Fixes: 769a29ce2af4 ("rtw88: 8821c: add basic functions").
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: stable@vger.kernel.org # 5.9+
> ---
> Kalle,
>
> This patch file was prepared a couple of months ago, but apparently not submitted
> then. It should be applied as soon as possible.
>
> Larry
Hi Larry,
This patch has been merged [1]. The git link of wireless driver next has been
changed [2]. That may be the reason you can't find the patch.
[1] https://lore.kernel.org/all/164364407205.21641.13263478436415544062.kvalo@kernel.org/
[2] git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
Ping-Ke
next prev parent reply other threads:[~2022-03-14 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 16:43 [PATCH] rtw88: Fix missing support for Realtek 8821CE RFE Type 6 Larry Finger
2022-03-14 0:21 ` Pkshih [this message]
2022-03-14 8:08 ` Kalle Valo
2022-03-14 16:58 ` Larry Finger
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=9ae5780119e24142bffd855d915a5e92@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@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.