All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sanjana Sanikommu <sanjana99reddy99@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] Staging: rtl8188eu: core: rtw_efuse.c: Line over 80 characters.
Date: Mon, 18 Mar 2019 18:40:07 +0100	[thread overview]
Message-ID: <20190318174007.GA22001@kroah.com> (raw)
In-Reply-To: <20190318160542.2803-1-sanjana99reddy99@gmail.com>

On Mon, Mar 18, 2019 at 09:35:42PM +0530, Sanjana Sanikommu wrote:
> Fix coding style issues, which solves checkpatch.pl warning:
> "WARNING: line over 80 characters".
> 
> Signed-off-by: Sanjana Sanikommu <sanjana99reddy99@gmail.com>
> ---
>  drivers/staging/rtl8188eu/core/rtw_efuse.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c b/drivers/staging/rtl8188eu/core/rtw_efuse.c
> index 51c3dd6d7ffb..a5d34b85d9c5 100644
> --- a/drivers/staging/rtl8188eu/core/rtw_efuse.c
> +++ b/drivers/staging/rtl8188eu/core/rtw_efuse.c
> @@ -794,13 +794,16 @@ bool Efuse_PgPacketWrite(struct adapter *pAdapter, u8 offset, u8 word_en, u8 *pD
>  
>  	hal_EfuseConstructPGPkt(offset, word_en, pData, &targetPkt);
>  
> -	if (!hal_EfusePartialWriteCheck(pAdapter, efuseType, &startAddr, &targetPkt))
> +	if (!hal_EfusePartialWriteCheck(pAdapter, efuseType,
> +					&startAddr, &targetPkt))

Why not use the full line:
	if (!hal_EfusePartialWriteCheck(pAdapter, efuseType, &startAddr,
					&targetPkt))

Only wrap where you _have_ to wrap, don't make lines shorter than they
have to unless it makes a lot of sense to.

thanks,

greg k-h


  reply	other threads:[~2019-03-18 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 16:05 [PATCH] Staging: rtl8188eu: core: rtw_efuse.c: Line over 80 characters Sanjana Sanikommu
2019-03-18 17:40 ` Greg KH [this message]
2019-03-18 17:50   ` sanjana99reddy99

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=20190318174007.GA22001@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=sanjana99reddy99@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.