From: Praveen Kumar <kpraveen.lkml@gmail.com>
To: Karolina Drobnik <karolinadrobnik@gmail.com>,
outreachy-kernel@googlegroups.com
Cc: gregkh@linuxfoundation.org, forest@alittletooquiet.net,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] [PATCH 2/7] staging: vt6655: Use incrementation in `idx`
Date: Fri, 29 Oct 2021 20:26:25 +0530 [thread overview]
Message-ID: <3dfc45e5-12bc-72da-a260-5551a483fe6e@gmail.com> (raw)
In-Reply-To: <c569952d92ba51f32679c2fd87fd48ad8e49e3fc.1635415820.git.karolinadrobnik@gmail.com>
On 28-10-2021 16:05, Karolina Drobnik wrote:
> Increment `idx` in a loop instead of adding the loop counter
> `i` to do so. Thanks to this change, the cast to unsigned short
> can be removed.
>
> Signed-off-by: Karolina Drobnik <karolinadrobnik@gmail.com>
> ---
> drivers/staging/vt6655/rf.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/vt6655/rf.c b/drivers/staging/vt6655/rf.c
> index f195dafb6e63..c07653566d17 100644
> --- a/drivers/staging/vt6655/rf.c
> +++ b/drivers/staging/vt6655/rf.c
> @@ -700,11 +700,11 @@ bool RFvWriteWakeProgSyn(struct vnt_private *priv, unsigned char rf_type,
> return false;
>
> for (i = 0; i < CB_AL2230_INIT_SEQ; i++)
> - MACvSetMISCFifo(priv, (unsigned short)(idx + i), al2230_init_table[i]);
> + MACvSetMISCFifo(priv, idx++, al2230_init_table[i]);
>
> - MACvSetMISCFifo(priv, (unsigned short)(idx + i), al2230_channel_table0[channel - 1]);
> + MACvSetMISCFifo(priv, idx++, al2230_channel_table0[channel - 1]);
> i++;
> - MACvSetMISCFifo(priv, (unsigned short)(idx + i), al2230_channel_table1[channel - 1]);
> + MACvSetMISCFifo(priv, idx++, al2230_channel_table1[channel - 1]);
> break;
>
> /* Need to check, PLLON need to be low for channel setting */
> @@ -717,17 +717,17 @@ bool RFvWriteWakeProgSyn(struct vnt_private *priv, unsigned char rf_type,
>
> if (channel <= CB_MAX_CHANNEL_24G) {
> for (i = 0; i < CB_AL7230_INIT_SEQ; i++)
> - MACvSetMISCFifo(priv, (unsigned short)(idx + i), al7230_init_table[i]);
> + MACvSetMISCFifo(priv, idx++, al7230_init_table[i]);
If I'm not wrong, there is a problem here, we are using the modified idx value here, instead of original which is *MISCFIFO_SYNDATA_IDX*.
I don't see idx value being reset either. Am I missing something ?
Further, this bring a question, how are you validating or planning to validate these changes ?
> } else {
> for (i = 0; i < CB_AL7230_INIT_SEQ; i++)
> - MACvSetMISCFifo(priv, (unsigned short)(idx + i), al7230_init_table_a_mode[i]);
> + MACvSetMISCFifo(priv, idx++, al7230_init_table_a_mode[i]);
> }
>
> - MACvSetMISCFifo(priv, (unsigned short)(idx + i), al7230_channel_table0[channel - 1]);
> + MACvSetMISCFifo(priv, idx++, al7230_channel_table0[channel - 1]);
> i++;
> - MACvSetMISCFifo(priv, (unsigned short)(idx + i), al7230_channel_table1[channel - 1]);
> + MACvSetMISCFifo(priv, idx++, al7230_channel_table1[channel - 1]);
> i++;
> - MACvSetMISCFifo(priv, (unsigned short)(idx + i), al7230_channel_table2[channel - 1]);
> + MACvSetMISCFifo(priv, idx++, al7230_channel_table2[channel - 1]);
> break;
>
> case RF_NOTHING:
>
Regards,
~Praveen.
next prev parent reply other threads:[~2021-10-29 14:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 10:35 [PATCH 0/7] staging: vt6655: Fix line wrapping in `RFvWriteWakeProgSyn` Karolina Drobnik
2021-10-28 10:35 ` [PATCH 1/7] staging: vt6655: Introduce `idx` temporary variable Karolina Drobnik
2021-10-29 14:47 ` [Outreachy kernel] " Praveen Kumar
2021-11-04 12:05 ` Dan Carpenter
2021-10-28 10:35 ` [PATCH 2/7] staging: vt6655: Use incrementation in `idx` Karolina Drobnik
2021-10-29 14:56 ` Praveen Kumar [this message]
2021-10-29 15:41 ` [Outreachy kernel] " Praveen Kumar
2021-11-01 9:47 ` Karolina Drobnik
2021-10-28 10:35 ` [PATCH 3/7] staging: vt6655: Remove unused `i` increments Karolina Drobnik
2021-10-28 10:35 ` [PATCH 4/7] staging: vt6655: Introduce `data` temporary variable Karolina Drobnik
2021-10-28 11:21 ` [Outreachy kernel] " Fabio M. De Francesco
2021-10-28 11:32 ` Julia Lawall
2021-10-28 11:48 ` Fabio M. De Francesco
2021-10-28 14:31 ` Karolina Drobnik
2021-10-28 14:40 ` Julia Lawall
2021-10-28 10:35 ` [PATCH 5/7] staging: vt6655: Rewrite conditional in AL7320 initialization Karolina Drobnik
2021-10-28 12:36 ` [Outreachy kernel] " Fabio M. De Francesco
2021-10-28 13:06 ` Julia Lawall
2021-10-28 14:35 ` Karolina Drobnik
2021-10-28 15:36 ` Fabio M. De Francesco
2021-10-28 10:35 ` [PATCH 6/7] staging: vt6655: Rename `RFvWriteWakeProgSyn` function Karolina Drobnik
2021-10-28 10:35 ` [PATCH 7/7] staging: vt6655: Update comment for `rf_write_wake_prog_syn` Karolina Drobnik
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=3dfc45e5-12bc-72da-a260-5551a483fe6e@gmail.com \
--to=kpraveen.lkml@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=karolinadrobnik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy-kernel@googlegroups.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
all inboxes | Powered by JetHome®