[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d1de60bd-c4c6-ebb1-1eac-a5eba41c9a78@i2se.com>
Date: Mon, 6 May 2019 18:28:48 +0200
From: Stefan Wahren <stefan.wahren@...e.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
Dan Carpenter <dan.carpenter@...cle.com>
Cc: devel@...verdev.osuosl.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
phil@...pberrypi.org, linux-kernel@...r.kernel.org,
Eric Anholt <eric@...olt.net>,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 2/3] staging: vchiq: revert "switch to
wait_for_completion_killable"
Hi Nicolas,
Am 06.05.19 um 17:59 schrieb Nicolas Saenz Julienne:
> Hi Dan, thanks for reviewing.
>
> On Mon, 2019-05-06 at 18:20 +0300, Dan Carpenter wrote:
>> On Mon, May 06, 2019 at 04:40:29PM +0200, Nicolas Saenz Julienne wrote:
>>> @@ -1740,7 +1740,8 @@ parse_rx_slots(struct vchiq_state *state)
>>> &service->bulk_rx : &service->bulk_tx;
>>>
>>> DEBUG_TRACE(PARSE_LINE);
>>> - if (mutex_lock_killable(&service->bulk_mutex)) {
>>> + if (mutex_lock_killable(
>>> + &service->bulk_mutex) != 0) {
>> This series does't add != 0 consistently... Personally, I would prefer
>> we just leave it out. I use != 0 for two things. 1) When I'm talking
>> about the number zero.
>>
>> if (len == 0) {
>>
>> Or with strcmp():
>>
>> if (strcmp(a, b) == 0) { // a equals b
>> if (strcmp(a, b) < 0) { // a less than b.
>>
>> But here zero means no errors, so I would just leave it out...
> I agree, I'll fix it.
i also agree with Dan, but this specific patch should revert the changes
of a772f116702e3f0afdd7e6acadc1b8fb3b20b9ff . So mentioned style issue
should be fixed in a separate patch.
Regards Stefan
>
> Regards,
> Nicolas
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Powered by blists - more mailing lists