From: Greg KH <gregkh@linuxfoundation.org>
To: Meng Tang <tangmeng@uniontech.com>
Cc: stable@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Ping-Ke Shih <pkshih@realtek.com>,
masterzorag <masterzorag@gmail.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Kalle Valo <kvalo@kernel.org>
Subject: Re: [PATCH 5.15 2/2] rtw88: rtw8821c: enable rfe 6 devices
Date: Thu, 30 Jun 2022 13:55:36 +0200 [thread overview]
Message-ID: <Yr2POPOQ7fYi08CL@kroah.com> (raw)
In-Reply-To: <20220630114621.19688-2-tangmeng@uniontech.com>
On Thu, Jun 30, 2022 at 07:46:21PM +0800, Meng Tang wrote:
> commit e109e3617e5d563b431a52e6e2f07f0fc65a93ae upstream.
>
> Ping-Ke Shih answered[1] a question for a user about an rtl8821ce device that
> reported RFE 6, which the driver did not support. Ping-Ke suggested a possible
> fix, but the user never reported back.
>
> A second user discovered the above thread and tested the proposed fix.
> Accordingly, I am pushing this change, even though I am not the author.
>
> [1] https://lore.kernel.org/linux-wireless/3f5e2f6eac344316b5dd518ebfea2f95@realtek.com/
>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> Reported-and-tested-by: masterzorag <masterzorag@gmail.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Signed-off-by: Kalle Valo <kvalo@kernel.org>
> Link: https://lore.kernel.org/r/20220107024739.20967-1-Larry.Finger@lwfinger.net
> Signed-off-by: Meng Tang <tangmeng@uniontech.com>
> ---
> drivers/net/wireless/realtek/rtw88/rtw8821c.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/wireless/realtek/rtw88/rtw8821c.c b/drivers/net/wireless/realtek/rtw88/rtw8821c.c
> index 746f6f8967d8..897da3ed2f02 100644
> --- a/drivers/net/wireless/realtek/rtw88/rtw8821c.c
> +++ b/drivers/net/wireless/realtek/rtw88/rtw8821c.c
> @@ -1513,6 +1513,7 @@ static const struct rtw_rfe_def rtw8821c_rfe_defs[] = {
> [0] = RTW_DEF_RFE(8821c, 0, 0),
> [2] = RTW_DEF_RFE_EXT(8821c, 0, 0, 2),
> [4] = RTW_DEF_RFE_EXT(8821c, 0, 0, 2),
> + [6] = RTW_DEF_RFE(8821c, 0, 0),
> };
>
> static struct rtw_hw_reg rtw8821c_dig[] = {
> --
> 2.20.1
>
>
>
Both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-06-30 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:46 [PATCH 5.15 1/2] rtw88: 8821c: support RFE type4 wifi NIC Meng Tang
2022-06-30 11:46 ` [PATCH 5.15 2/2] rtw88: rtw8821c: enable rfe 6 devices Meng Tang
2022-06-30 11:55 ` Greg KH [this message]
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=Yr2POPOQ7fYi08CL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masterzorag@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=stable@vger.kernel.org \
--cc=tangmeng@uniontech.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