From: Randy Dunlap <rdunlap@infradead.org>
To: Joe Perches <joe@perches.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Greg KH <gregkh@linuxfoundation.org>,
Andy Whitcroft <apw@shadowen.org>
Cc: Joshua Abraham <j.abraham1776@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fsl-dpaa2: Fix multiple assignments should be avoided
Date: Wed, 8 Nov 2017 09:16:02 -0800 [thread overview]
Message-ID: <eeb892dd-3b21-e43c-ae97-745b7b69fa29@infradead.org> (raw)
In-Reply-To: <1510141182.15768.17.camel@perches.com>
On 11/08/2017 03:39 AM, Joe Perches wrote:
> On Wed, 2017-11-08 at 12:40 +0300, Dan Carpenter wrote:
>> On Wed, Nov 08, 2017 at 10:20:48AM +0100, Greg KH wrote:
>>> On Tue, Nov 07, 2017 at 07:45:03PM -0500, Joshua Abraham wrote:
>>>> This patch fixes the checkpatch.pl warning:
>>>> "CHECK: multiple assignments should be avoided"
>>>>
>>>> Signed-off-by: Joshua Abraham <j.abraham1776@gmail.com>
>>>> ---
>>>> drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c | 3 ++-
>>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c b/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
>>>> index 0d8ed002adcb..384218946108 100644
>>>> --- a/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
>>>> +++ b/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
>>>> @@ -1661,7 +1661,8 @@ static void set_fq_affinity(struct dpaa2_eth_priv *priv)
>>>> * This may well change at runtime, either through irqbalance or
>>>> * through direct user intervention.
>>>> */
>>>> - rx_cpu = txc_cpu = cpumask_first(&priv->dpio_cpumask);
>>>> + rx_cpu = cpumask_first(&priv->dpio_cpumask);
>>>> + txc_cpu = rx_cpu;
>>>
>>> The original code here makes much more sense, doesn't it?
>>>
>>> Sometimes checkpatch is wrong :)
>>
>> It feels like the majority of these multiple assignment warnings are
>> wrong. I thought it would be a good idea at first but after looking at
>> a bunch of the patches it feels like we should just remove the check.
>
> I don't have a particular opinion one way or another.
>
> That bit was added to CodingStyle by Randy Dunlap back
> in 2006 by
>
> commit b3fc9941fbc6efe5cb77728adb0fb12be363e73e
> Author: Randy Dunlap <randy.dunlap@oracle.com>
> Date: Sun Dec 10 02:18:56 2006 -0800
>
> [PATCH] CodingStyle updates
>
> Add some kernel coding style comments, mostly pulled from emails
> by Andrew Morton, Jesper Juhl, and Randy Dunlap.
>
> - add paragraph on switch/case indentation (with fixes)
> - add paragraph on multiple-assignments
> - add more on Braces
> - add section on Spaces; add typeof, alignof, & __attribute__ with sizeof;
> add more on postfix/prefix increment/decrement operators
> - add paragraph on function breaks in source files; add info on
> function prototype parameter names
> - add paragraph on EXPORT_SYMBOL placement
> - add section on /*-comment style, long-comment style, and data
> declarations and comments
> - correct some chapter number references that were missed when
> chapters were renumbered
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Acked-by: Jesper Juhl <jesper.juhl@gmail.com>
> Acked-by: Jan Engelhardt <jengelh@gmx.de>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
So it was. I would certainly support removing it.
I suspect I copied that from someone else's email. My personal style
would be to allow that.
--
~Randy
next prev parent reply other threads:[~2017-11-08 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 0:45 Joshua Abraham
2017-11-08 9:20 ` Greg KH
2017-11-08 9:40 ` Dan Carpenter
2017-11-08 11:39 ` Joe Perches
2017-11-08 17:16 ` Randy Dunlap [this message]
2017-11-08 17:30 ` Joe Perches
2017-11-08 14:59 ` Josh Abraham
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=eeb892dd-3b21-e43c-ae97-745b7b69fa29@infradead.org \
--to=rdunlap@infradead.org \
--cc=apw@shadowen.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=j.abraham1776@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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®