[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b89bfd5c-315a-345f-7239-2d6300cf1f6e@users.sourceforge.net>
Date: Sun, 23 Apr 2017 13:10:16 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>,
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()
>> 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.
Why do you find the sentence for the multiplication information inappropriate
(or incomplete) at the moment?
> Another sentence explaining why this is bad/undesirable.
Which details do you miss here?
> In this case, the output of the checkpatch script would come in handy.
Its implementation of the check “ALLOC_WITH_MULTIPLY” considers only an other
search pattern so far.
* Do you find it worthwhile to add a prefix like “devm_” to the used
regular expression?
* Would like to improve any related scripts for the semantic patch language
(Coccinelle software) a bit more?
> With this, you avoid cramming every information into one long and
> complicated sentence.
Thanks for your feedback about other wording preferences.
Regards,
Markus
Powered by blists - more mailing lists