Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1045119AbdDWKoW (ORCPT ); Sun, 23 Apr 2017 06:44:22 -0400 Received: from smtp.math.uni-bielefeld.de ([129.70.45.10]:47099 "EHLO smtp.math.uni-bielefeld.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1044993AbdDWKoP (ORCPT ); Sun, 23 Apr 2017 06:44:15 -0400 Subject: Re: s3c24xx: Use devm_kcalloc() in s3c24xx_dma_probe() To: SF Markus Elfring , dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org Cc: Dan Williams , Javier Martinez Canillas , Krzysztof Kozlowski , Kukjin Kim , LKML , kernel-janitors@vger.kernel.org References: <930f0a6c-bc5c-3d01-6814-563780fc90ef@users.sourceforge.net> <9c10b823-f49b-8c73-2bf8-0fd2b0ba0231@users.sourceforge.net> <02134825-fec7-73d7-2eb6-b510eaaf3b08@users.sourceforge.net> From: Tobias Jakobi Message-ID: <49f1c0b2-7463-2121-1aed-0998f6635c92@math.uni-bielefeld.de> Date: Sun, 23 Apr 2017 12:44:11 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: <02134825-fec7-73d7-2eb6-b510eaaf3b08@users.sourceforge.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1213 Lines: 34 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 >