[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <edf839ce-cc61-73dc-e017-b49648b94d1c@web.de>
Date: Tue, 12 May 2020 13:40:57 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Bernard Zhao <bernard@...o.com>,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org,
linux-samsung-soc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, opensource.kernel@...o.com,
Krzysztof Kozlowski <krzk@...nel.org>,
Kukjin Kim <kgene@...nel.org>,
Lukasz Luba <lukasz.luba@....com>
Subject: Re: [PATCH v2] memory/samsung: reduce unnecessary mutex lock area
> Maybe dmc->df->lock seems not needed to protect "if (ret)
> & dev_warn" branch. Maybe this change speed up the code a bit.
I suggest to improve also this commit message.
* Please reduce uncertainty.
* An imperative wording is probably preferred, isn't it?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=152036d1379ffd6985262743dcf6b0f9c75f83a4#n151
* Will it be more appropriate to refer to the transformation “Reduce the lock scope”?
* Would you like to add the tag “Fixes” to the change description?
Regards,
Markus
Powered by blists - more mailing lists