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>, Jiajie Chen <c@jia.je>
Subject: RE: [PATCH v2] wifi: rtl8xxxu: Support new chip RTL8710BU aka RTL8188GU
Date: Mon, 13 Mar 2023 02:11:49 +0000	[thread overview]
Message-ID: <0e08c94a0a2447eb935a65e0b44d172a@realtek.com> (raw)
In-Reply-To: <07f780e8-7b9e-c3cf-02dd-48325bd1f3b7@gmail.com>



> -----Original Message-----
> From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Sent: Saturday, March 11, 2023 1:53 AM
> To: Ping-Ke Shih <pkshih@realtek.com>; linux-wireless@vger.kernel.org
> Cc: Jes Sorensen <Jes.Sorensen@gmail.com>; Jiajie Chen <c@jia.je>
> Subject: Re: [PATCH v2] wifi: rtl8xxxu: Support new chip RTL8710BU aka RTL8188GU
> 
> On 10/03/2023 02:49, Ping-Ke Shih wrote:
> >
> > 2. drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_8710b.c:1487 rtl8710bu_phy_iq_calibrate() error:
> uninitialized symbol 'reg_e94'.
> >
> > This could be a false-alarm too. 'reg_e94' must be set if 'candidate >= 0', but
> > original statement causes smatch hard to determine:
> >
> >    if (reg_e94 && candidate >= 0)
> >
> > swap the expressions to fix the warning:
> >
> >   if (candidate >= 0 && reg_e94)
> >
> 
> Moving "if (reg_e94)" inside the previous "if (candidate >= 0)" should also
> fix it, I think.
> 
>         if (candidate >= 0) {
>                 reg_e94 = result[candidate][0];
>                 reg_e9c = result[candidate][1];
>                 reg_ea4 = result[candidate][2];
>                 reg_eac = result[candidate][3];
> 
>                 dev_dbg(dev, "%s: candidate is %x\n", __func__, candidate);
>                 dev_dbg(dev, "%s: e94=%x e9c=%x ea4=%x eac=%x\n",
>                         __func__, reg_e94, reg_e9c, reg_ea4, reg_eac);
> 
>                 path_a_ok = true;
> 
>                 if (reg_e94)
>                         rtl8xxxu_fill_iqk_matrix_a(priv, path_a_ok, result,
>                                                    candidate, (reg_ea4 == 0));
>         }
> 

Indeed, I have confirmed it works.



      reply	other threads:[~2023-03-13  2:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 21:27 [PATCH v2] wifi: rtl8xxxu: Support new chip RTL8710BU aka RTL8188GU Bitterblue Smith
2023-03-08 23:18 ` philipp hortmann
2023-03-10  0:49 ` Ping-Ke Shih
2023-03-10 17:53   ` Bitterblue Smith
2023-03-13  2:11     ` Ping-Ke Shih [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=0e08c94a0a2447eb935a65e0b44d172a@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=c@jia.je \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rtl8821cerfe2@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