All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Namrata A Shettar <namrataashettar@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
	Malcolm Priestley <tvboxspy@gmail.com>,
	Anson Jacob <ansonjacob.aj@gmail.com>,
	Haneen Mohammed <hamohammed.sa@gmail.com>,
	outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH v2 3/4] staging: vt6655: card: Break multiple assignments
Date: Sun, 18 Sep 2016 12:40:59 +0200	[thread overview]
Message-ID: <20160918104059.GA10846@kroah.com> (raw)
In-Reply-To: <fe7f635d9b75bb93286245415d4a54497a8a4842.1474187686.git.namrataashettar@gmail.com>

On Sun, Sep 18, 2016 at 02:35:39PM +0530, Namrata A Shettar wrote:
> Break multiple assignments on same line to resolve checkpatch issue.
> 
> Signed-off-by: Namrata A Shettar <namrataashettar@gmail.com>
> ---
>  drivers/staging/vt6655/card.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/vt6655/card.c b/drivers/staging/vt6655/card.c
> index afb1e8b..00e7858 100644
> --- a/drivers/staging/vt6655/card.c
> +++ b/drivers/staging/vt6655/card.c
> @@ -528,8 +528,10 @@ CARDvSafeResetTx(
>  	struct vnt_tx_desc *pCurrTD;
>  
>  	/* initialize TD index */
> -	priv->apTailTD[0] = priv->apCurrTD[0] = &(priv->apTD0Rings[0]);
> -	priv->apTailTD[1] = priv->apCurrTD[1] = &(priv->apTD1Rings[0]);
> +        priv->apCurrTD[0] = &(priv->apTD0Rings[0]);
> +	priv->apTailTD[0] = priv->apCurrTD[0];
> +        priv->apCurrTD[1] = &(priv->apTD1Rings[0]);
> +	priv->apTailTD[1] = priv->apCurrTD[1];

Does that look correct to you?

(hint, odd indentation)

And really, the original code is fine, I would recommend just leaving
this alone, it makes more sense as-is, don't you think?

thanks,

greg k-h


  reply	other threads:[~2016-09-18 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18  9:04 [PATCH v2 0/4] staging: vt6655: Fix checkpatch issues Namrata A Shettar
2016-09-18  9:04 ` [PATCH v2 1/4] staging: vt6655: device_main: Replace NULL comparison with !x Namrata A Shettar
2016-09-18  9:05 ` [PATCH v2 2/4] staging: vt6655: device_main: Replace explicit NULL comparison Namrata A Shettar
2016-09-18  9:05 ` [PATCH v2 3/4] staging: vt6655: card: Break multiple assignments Namrata A Shettar
2016-09-18 10:40   ` Greg Kroah-Hartman [this message]
2016-09-18 10:54     ` Namrata A Shettar
2016-09-18 11:07       ` [Outreachy kernel] " Greg Kroah-Hartman
2016-09-18 11:13         ` Namrata A Shettar
2016-09-18  9:05 ` [PATCH v2 4/4] staging: vt6655: device_main: Break up " Namrata A Shettar
2016-09-18 10:41   ` Greg Kroah-Hartman
2016-09-18 10:56     ` Namrata A Shettar

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=20160918104059.GA10846@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ansonjacob.aj@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=hamohammed.sa@gmail.com \
    --cc=namrataashettar@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=tvboxspy@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.