From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751577AbdJSGWh (ORCPT ); Thu, 19 Oct 2017 02:22:37 -0400 Received: from mail-pg0-f68.google.com ([74.125.83.68]:44589 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750985AbdJSGWe (ORCPT ); Thu, 19 Oct 2017 02:22:34 -0400 X-Google-Smtp-Source: ABhQp+QLz4iZTMN2kZEfGBGSIoxA2HEC3pxTXQ0HTlt7y5/iycT4CKIaJ6f9qy53+o4tPsRZiK0b4g== Subject: Re: [PATCH v3] staging: ccree: fix boolreturn.cocci warning To: "Tobin C. Harding" Cc: gilad@benyossef.com, gregkh@linuxfoundation.org, linux-crypto@vger.kernel.org, driverdev-devel@linuxdriverproject.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, karthik@techveda.org References: <20171018023607.GE30848@eros> <1508308915-18789-1-git-send-email-sunil.m@techveda.org> <20171018205450.GB31318@eros> From: Suniel Mahesh Message-ID: Date: Thu, 19 Oct 2017 11:52:29 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171018205450.GB31318@eros> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 19 October 2017 02:24 AM, Tobin C. Harding wrote: > Hi Suniel, > > Well done with you continued versions. I am being particularly nit picky here but since we are > striving for perfection I'm sure will humour me. If English is not your first language please > forgive me for picking you up on language subtleties. Hi Tobin, First of all, I thank you very much for the reviews, to be honest I enjoyed the process. Yes all of us, here we are striving for perfection. I am always open to take suggestions from the community to improve things which I am working on and there by improving myself. Yeah English is not my first language, but all my education was done in English, no issues there. > > On Wed, Oct 18, 2017 at 12:11:55PM +0530, sunil.m@techveda.org wrote: >> From: Suniel Mahesh >> >> This fixes the following coccinelle warning: >> WARNING: return of 0/1 in function 'ssi_is_hw_key' with return type bool. > > This should be a description of the problem, so saying _why_ there is a problem or _what_ is wrong > with the code currently that warrants a patch. Sometimes while describing the problem you may > include descriptions of the solution especially it is not immediately obvious why your proposed > solution fixes the issue being explained. As an extra we shouldn't ever say 'This patch ...' or > 'This does xyz'. > >> return "false" instead of 0. > > Perfect, this is in imperative mood. Spot on! > >> Signed-off-by: Suniel Mahesh >> --- >> Changes for v3: >> - Changed the commit log even more to give an accurate >> description of the changeset as suggested by Toby C.Harding. > > My name is Tobin :) how did I blind myself, my bad, will be careful and avoid such mistakes moving forward. > >> --- >> Changes for v2: >> - Changed the commit log to give a more accurate description >> of the changeset as suggested by Toby C.Harding. >> --- >> Note: >> - Patch was built(ARCH=arm) on latest linux-next. >> - No build issues reported, however it was not >> tested on real hardware. >> - Please discard this changeset, if this is not >> helping the code look better. >> --- >> drivers/staging/ccree/ssi_cipher.h | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/drivers/staging/ccree/ssi_cipher.h b/drivers/staging/ccree/ssi_cipher.h >> index c9a83df..f499962 100644 >> --- a/drivers/staging/ccree/ssi_cipher.h >> +++ b/drivers/staging/ccree/ssi_cipher.h >> @@ -75,7 +75,7 @@ struct arm_hw_key_info { >> >> static inline bool ssi_is_hw_key(struct crypto_tfm *tfm) >> { >> - return 0; >> + return false; >> } >> >> #endif /* CRYPTO_TFM_REQ_HW_KEY */ >> -- >> 1.9.1 >> > > For what it's worth, Reviewed-by: Tobin C. Harding > > As stated I am being particularly 'nit picky', the commit log is _probably_ good enough to be > merged, I am not a maintainer though so it's not really anything to do with me. I do know however > that sometimes patches go to the bottom of Greg's list if they have comments/suggestions. I mention > this only so you learn more about the process and to help you with successfully getting you patches > merged. Keep up the work! Thanks once again Tobin, I love feedback and that's how we can make this world a better workplace. Suniel > > Good luck, > Tobin. >