From: Greg KH <gregkh@linuxfoundation.org>
To: Karolina Drobnik <karolinadrobnik@gmail.com>
Cc: outreachy-kernel@googlegroups.com, forest@alittletooquiet.net,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6655: Fix line wrapping in rf.c file
Date: Mon, 18 Oct 2021 17:12:31 +0200 [thread overview]
Message-ID: <YW2O3wC8wMEKS3Ub@kroah.com> (raw)
In-Reply-To: <20211018150526.9718-1-karolinadrobnik@gmail.com>
On Mon, Oct 18, 2021 at 04:05:26PM +0100, Karolina Drobnik wrote:
> Fix line length warnings raised by checkpatch.pl in
> rf.c file for `RFvWriteWakeProgSyn`,`RFbRawSetPower`
> and `RFbAL7230SelectChannelPostProcess`functions.
>
> Signed-off-by: Karolina Drobnik <karolinadrobnik@gmail.com>
> ---
> drivers/staging/vt6655/rf.c | 66 +++++++++++++++++++++++++++----------
> 1 file changed, 49 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/staging/vt6655/rf.c b/drivers/staging/vt6655/rf.c
> index a6f17162d017..206d34b555bc 100644
> --- a/drivers/staging/vt6655/rf.c
> +++ b/drivers/staging/vt6655/rf.c
> @@ -699,11 +699,17 @@ bool RFvWriteWakeProgSyn(struct vnt_private *priv, unsigned char byRFType,
> return false;
>
> for (ii = 0; ii < CB_AL2230_INIT_SEQ; ii++)
> - MACvSetMISCFifo(priv, (unsigned short)(MISCFIFO_SYNDATA_IDX + ii), dwAL2230InitTable[ii]);
> + MACvSetMISCFifo(priv,
> + (unsigned short)(MISCFIFO_SYNDATA_IDX + ii),
> + dwAL2230InitTable[ii]);
>
> - MACvSetMISCFifo(priv, (unsigned short)(MISCFIFO_SYNDATA_IDX + ii), dwAL2230ChannelTable0[uChannel - 1]);
> + MACvSetMISCFifo(priv,
> + (unsigned short)(MISCFIFO_SYNDATA_IDX + ii),
> + dwAL2230ChannelTable0[uChannel - 1]);
> ii++;
> - MACvSetMISCFifo(priv, (unsigned short)(MISCFIFO_SYNDATA_IDX + ii), dwAL2230ChannelTable1[uChannel - 1]);
> + MACvSetMISCFifo(priv,
> + (unsigned short)(MISCFIFO_SYNDATA_IDX + ii),
> + dwAL2230ChannelTable1[uChannel - 1]);
> break;
>
> /* Need to check, PLLON need to be low for channel setting */
> @@ -716,17 +722,28 @@ bool RFvWriteWakeProgSyn(struct vnt_private *priv, unsigned char byRFType,
>
> if (uChannel <= CB_MAX_CHANNEL_24G) {
> for (ii = 0; ii < CB_AL7230_INIT_SEQ; ii++)
> - MACvSetMISCFifo(priv, (unsigned short)(MISCFIFO_SYNDATA_IDX + ii), dwAL7230InitTable[ii]);
> + MACvSetMISCFifo(priv,
> + (unsigned short)(MISCFIFO_SYNDATA_IDX
> + + ii), dwAL7230InitTable[ii]);
You shouldn't put the "+" on the start of a new line.
Also, these are all just fine as-is for now. A better way to make these
lines smaller is to use better variable and function names that are
shorter and make sense :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-10-18 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 15:05 [PATCH] staging: vt6655: Fix line wrapping in rf.c file Karolina Drobnik
2021-10-18 15:10 ` [Outreachy kernel] " Julia Lawall
2021-10-18 15:12 ` Greg KH [this message]
2021-10-19 5:56 ` Joe Perches
2021-10-19 10:59 ` Karolina Drobnik
2021-10-19 11:12 ` Greg KH
2021-10-19 12:26 ` Joe Perches
2021-10-19 13:12 ` [Outreachy kernel] " Fabio M. De Francesco
2021-10-19 13:07 ` Fabio M. De Francesco
2021-10-19 15:08 ` 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=YW2O3wC8wMEKS3Ub@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=forest@alittletooquiet.net \
--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