From: Ping-Ke Shih <pkshih@realtek.com>
To: Jun ASAKA <JunASAKA@zzy040330.moe>,
"Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>
Cc: "kvalo@kernel.org" <kvalo@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v5] wifi: rtl8xxxu: fixing IQK failures for rtl8192eu
Date: Wed, 7 Dec 2022 03:55:16 +0000 [thread overview]
Message-ID: <159ac3a296164b05b319bfb254a7901b@realtek.com> (raw)
In-Reply-To: <b4b65c74-792f-4df1-18bf-5c6f80845814@zzy040330.moe>
> -----Original Message-----
> From: Jun ASAKA <JunASAKA@zzy040330.moe>
> Sent: Wednesday, December 7, 2022 11:51 AM
> To: Ping-Ke Shih <pkshih@realtek.com>; Jes.Sorensen@gmail.com
> Cc: kvalo@kernel.org; davem@davemloft.net; edumazet@google.com; kuba@kernel.org; pabeni@redhat.com;
> linux-wireless@vger.kernel.org; netdev@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v5] wifi: rtl8xxxu: fixing IQK failures for rtl8192eu
>
> On 07/12/2022 11:43, Ping-Ke Shih wrote:
> >
> >> -----Original Message-----
> >> From: Jun ASAKA <JunASAKA@zzy040330.moe>
> >> Sent: Wednesday, December 7, 2022 11:39 AM
> >> To: Jes.Sorensen@gmail.com
> >> Cc: kvalo@kernel.org; davem@davemloft.net; edumazet@google.com; kuba@kernel.org; pabeni@redhat.com;
> >> linux-wireless@vger.kernel.org; netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Jun ASAKA
> >> <JunASAKA@zzy040330.moe>; Ping-Ke Shih <pkshih@realtek.com>
> >> Subject: [PATCH v5] wifi: rtl8xxxu: fixing IQK failures for rtl8192eu
> >>
> >> Fixing "Path A RX IQK failed" and "Path B RX IQK failed"
> >> issues for rtl8192eu chips by replacing the arguments with
> >> the ones in the updated official driver as shown below.
> >> 1. https://github.com/Mange/rtl8192eu-linux-driver
> >> 2. vendor driver version: 5.6.4
> >>
> >> Tested-by: Jun ASAKA <JunASAKA@zzy040330.moe>
> >> Signed-off-by: Jun ASAKA <JunASAKA@zzy040330.moe>
> >> Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
> >> ---
> >> v5:
> >> - no modification.
> > Then, why do you need v5?
> Well, I just want to add the "Reviewed-By" line to the commit message.
> Sorry for the noise if there is no need to do that.
>
No need to add "Reviewed-By". Kalle will add it when this patch gets merged.
Ping-Ke
next prev parent reply other threads:[~2022-12-07 3:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 3:39 [PATCH v5] wifi: rtl8xxxu: fixing IQK failures for rtl8192eu Jun ASAKA
2022-12-07 3:43 ` Ping-Ke Shih
2022-12-07 3:50 ` Jun ASAKA
2022-12-07 3:55 ` Ping-Ke Shih [this message]
2022-12-07 4:01 ` Jun ASAKA
2022-12-07 12:31 ` Kalle Valo
2022-12-08 14:53 ` [v5] " Kalle Valo
2022-12-09 3:46 ` Jun ASAKA
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=159ac3a296164b05b319bfb254a7901b@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=JunASAKA@zzy040330.moe \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).