All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Varsha Rao <rvarsha016@gmail.com>
Cc: forest@alittletooquiet.net, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] staging: vt6655: Fix line over 80 characters.
Date: Fri, 14 Oct 2016 09:27:54 +0200	[thread overview]
Message-ID: <20161014072754.GA5464@kroah.com> (raw)
In-Reply-To: <20161013215008.GA21291@euri>

On Fri, Oct 14, 2016 at 03:21:24AM +0530, Varsha Rao wrote:
> This patch fixes the checkpatch warning of line over 80 characters.
> 
> Signed-off-by: Varsha Rao <rvarsha016@gmail.com>
> ---
>  drivers/staging/vt6655/mac.c |   3 +-
>  drivers/staging/vt6655/rf.c  | 737 +++++++++++++++++++++++++++++--------------
>  2 files changed, 495 insertions(+), 245 deletions(-)
> 
> diff --git a/drivers/staging/vt6655/mac.c b/drivers/staging/vt6655/mac.c
> index 4aaa99b..23de67c 100644
> --- a/drivers/staging/vt6655/mac.c
> +++ b/drivers/staging/vt6655/mac.c
> @@ -315,7 +315,8 @@ bool MACbSoftwareReset(struct vnt_private *priv)
>   */
>  bool MACbSafeSoftwareReset(struct vnt_private *priv)
>  {
> -	unsigned char abyTmpRegData[MAC_MAX_CONTEXT_SIZE_PAGE0 + MAC_MAX_CONTEXT_SIZE_PAGE1];
> +	unsigned char abyTmpRegData[MAC_MAX_CONTEXT_SIZE_PAGE0 +
> +				    MAC_MAX_CONTEXT_SIZE_PAGE1];
>  	bool bRetVal;
>  
>  	/* PATCH....
> diff --git a/drivers/staging/vt6655/rf.c b/drivers/staging/vt6655/rf.c
> index 1762c05..2e0e0c2 100644
> --- a/drivers/staging/vt6655/rf.c
> +++ b/drivers/staging/vt6655/rf.c
> @@ -63,37 +63,65 @@ static const unsigned long dwAL2230InitTable[CB_AL2230_INIT_SEQ] = {
>  };
>  
>  static const unsigned long dwAL2230ChannelTable0[CB_MAX_CHANNEL] = {
> -	0x03F79000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 1, Tf = 2412MHz */
> -	0x03F79000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 2, Tf = 2417MHz */
> -	0x03E79000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 3, Tf = 2422MHz */
> -	0x03E79000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 4, Tf = 2427MHz */
> -	0x03F7A000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 5, Tf = 2432MHz */
> -	0x03F7A000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 6, Tf = 2437MHz */
> -	0x03E7A000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 7, Tf = 2442MHz */
> -	0x03E7A000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 8, Tf = 2447MHz */
> -	0x03F7B000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 9, Tf = 2452MHz */
> -	0x03F7B000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 10, Tf = 2457MHz */
> -	0x03E7B000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 11, Tf = 2462MHz */
> -	0x03E7B000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 12, Tf = 2467MHz */
> -	0x03F7C000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW, /* channel = 13, Tf = 2472MHz */
> -	0x03E7C000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW  /* channel = 14, Tf = 2412M */
> +	/* channel = 1, Tf = 2412MHz */
> +	0x03F79000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW,
> +	/* channel = 2, Tf = 2417MHz */
> +	0x03F79000 + (BY_AL2230_REG_LEN << 3) + IFREGCTL_REGW,
> +	/* channel = 3, Tf = 2422MHz */

People keep trying to "fix" these lines.  Please just leave them as-is,
it's much easier to read them in the old way, right?  And that takes
precedence over the "obey checkpatch.pl" movement.

thanks,

greg k-h


  reply	other threads:[~2016-10-14  7:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 21:51 [PATCH] staging: vt6655: Fix line over 80 characters Varsha Rao
2016-10-14  7:27 ` Greg KH [this message]
2016-10-20 18:10   ` Varsha Rao
2016-10-24 13:29     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2019-03-04  1:19 [PATCH] Staging: " Madhumitha Prabakaran
2019-03-04  7:45 ` Greg KH
2019-03-04 16:00   ` Madhumthia Prabakaran
2019-03-04  1:29 Madhumitha Prabakaran

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=20161014072754.GA5464@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=forest@alittletooquiet.net \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=rvarsha016@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.