[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49f1c0b2-7463-2121-1aed-0998f6635c92@math.uni-bielefeld.de>
Date: Sun, 23 Apr 2017 12:44:11 +0200
From: Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>,
dmaengine@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org
Cc: Dan Williams <dan.j.williams@...el.com>,
Javier Martinez Canillas <javier@....samsung.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
Kukjin Kim <kgene@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: s3c24xx: Use devm_kcalloc() in s3c24xx_dma_probe()
SF Markus Elfring wrote:
>>> * A multiplication for the size determination of a memory allocation
>>> indicated that an array data structure should be processed.
>>> Thus use the corresponding function "devm_kcalloc".
>> I have trouble parsing that sentences. This looks like the typical
>> approach of native german speakers to directly transfer sentence
>> constructions from German to English. Which, in most cases, doesn't work
>> or is just plain confusing.
>
> Do you find the following wording better to understand
> if it would be presented by a script like “checkpatch.pl”?
>
> WARNING: Prefer devm_kcalloc over devm_kzalloc with multiply
For example. Also I just noticed some previous comment by Krzysztof that
pointed that out already.
My suggestion: One sentence describing that the current situation is.
Another sentence explaining why this is bad/undesirable. Last sentence
saying what you're doing to fix this (can sometimes be omitted if it's
clear from the diffstat). In this case, the output of the checkpatch
script would come in handy.
With this, you avoid cramming every information into one long and
complicated sentence.
With best wishes,
Tobias
>
>
> Regards,
> Markus
>
Powered by blists - more mailing lists