[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f0c5eb0-e7c2-9c27-387a-e62b19f0578a@users.sourceforge.net>
Date: Mon, 19 Mar 2018 10:51:43 +0100
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Jonathan Cameron <jic23@...nel.org>, linux-iio@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Pravin Shedge <pravin.shedge4linux@...il.com>,
Quentin Schulz <quentin.schulz@...e-electrons.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: iio/gyro/bmg160_core: Improve unlocking of a mutex in five
functions
>> The mutex was (and is still only) locked within case branches, isn't it?
>>
> You are correct, this does however reflect the issue with the resulting
> lack of balance here.
I suggest to reconsider affected software aspects a bit more.
> I saw the mutex was getting unlocked outside the local scope and so assumed
> that it was also take outside the local scope.
Assumptions and corresponding expectations might need further clarifications.
> That isn't true, so we have hurt readability.
Does your conclusion need any adjustment?
> I read it quickly and got the wrong idea which generally implies it is not
> as clear as we would like.
>
> Hence this change isn't going anywhere I'm afraid.
I imagine that more time will be needed then to get used to additional adjustments
of implementation details in these functions.
Regards,
Markus
Powered by blists - more mailing lists