From: Saurav Girepunje <saurav.girepunje@gmail.com>
To: Pavel Skripkin <paskripkin@gmail.com>,
Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
gregkh@linuxfoundation.org, alec@vc-celle.de,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: saurav.girepunje@hotmail.com
Subject: Re: [PATCH] staging: rtl8712: remove the condition with no effect
Date: Sun, 31 Oct 2021 15:05:02 +0530 [thread overview]
Message-ID: <bf93fce2-6669-1e0e-3117-c84e7e7b4de9@gmail.com> (raw)
In-Reply-To: <d4ee4591-0642-002b-ddd8-41693c0f1ccb@gmail.com>
On 28/10/21 4:56 pm, Pavel Skripkin wrote:
> On 10/28/21 07:31, Saurav Girepunje wrote:
>> Remove the if condition check and else code section in
>> query_rx_phy_status(). As variable cck_highpwr is assign a value of '0'
>> after this assignment, if condition check !cck_highpwr is always
>> going to be true. So remove the if condition check as well as else
>> section which will be never true.
>>
>> After removing the if condition there is no use of local variable
>> cck_highpwr. Remove the local variable cck_highpwr.
>>
>> Signed-off-by: Saurav Girepunje <saurav.girepunje@gmail.com>
>> ---
>
> [code snip]
>
>> + report = pcck_buf->cck_agc_rpt & 0xc0;
>> + report >>= 6;
>> + switch (report) {
>> + /* Modify the RF RNA gain value to -40, -20,
>> + * -2, 14 by Jenyu's suggestion
>> + * Note: different RF with the different
>> + * RNA gain.
>> + */
>> + case 0x3:
>> + rx_pwr_all = -40 - (pcck_buf->cck_agc_rpt &
>> + 0x3e);
>
> You can move "0x3e);" part on previous line, since it will fit even 80 characters boundary. It will improve readability, IMO
>
> Same below.
>
Yes, This is also can be done on same patch.
Thanks for review Pavel
>> + break;
>> + case 0x2:
>> + rx_pwr_all = -20 - (pcck_buf->cck_agc_rpt &
>> + 0x3e);
>> + break;
>> + case 0x1:
>> + rx_pwr_all = -2 - (pcck_buf->cck_agc_rpt &
>> + 0x3e);
>> + break;
>> + case 0x0:
>> + rx_pwr_all = 14 - (pcck_buf->cck_agc_rpt &
>> + 0x3e);
>> + break;
>> }
>> +
>
>
>
> With regards,
> Pavel Skripkin
Regards,
Saurav
prev parent reply other threads:[~2021-10-31 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 4:31 [PATCH] staging: rtl8712: remove the condition with no effect Saurav Girepunje
2021-10-28 11:26 ` Pavel Skripkin
2021-10-31 9:35 ` Saurav Girepunje [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=bf93fce2-6669-1e0e-3117-c84e7e7b4de9@gmail.com \
--to=saurav.girepunje@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=alec@vc-celle.de \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paskripkin@gmail.com \
--cc=saurav.girepunje@hotmail.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