[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16c50966-66f2-8a08-0ebc-936b04311f14@users.sourceforge.net>
Date: Mon, 26 Sep 2016 14:28:58 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Paul Bolle <pebolle@...cali.nl>
Cc: netdev@...r.kernel.org, Karsten Keil <isdn@...ux-pingi.de>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Julia Lawall <julia.lawall@...6.fr>
Subject: Re: ISDN-CAPI: Adjust 17 function calls together with variable
assignments
>> The script "checkpatch.pl" can point out that assignments should usually
>> not be performed within condition checks.
>> Thus move the assignment for a variable to a separate statement
>> in four functions.
>
> Did you recycle this commit explanation?
Yes. - I am going to use similar commit messages for further changes
in other software modules.
> Because git diff tells me you actually touched about eight functions.
You are right. - I'm sorry that I overlooked to update this number somehow.
> scripts/checkpatch.pl -f drivers/isdn/capi/capidrv.c | grep "assignment in if condition" | wc -l
>
> It tells me there are actually 18 instances of this "ERROR".
> Why did you ignore one of it in this patch?
Did I accidentally leave another update candidate over?
* How do you think about to pick such a software update opportunity up?
* Do you expect a resend for the steps 3 - 5 of this small patch series?
Regards,
Markus
Powered by blists - more mailing lists