Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751790AbbE0B5G (ORCPT ); Tue, 26 May 2015 21:57:06 -0400 Received: from smtprelay0159.hostedemail.com ([216.40.44.159]:51984 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751472AbbE0B5E (ORCPT ); Tue, 26 May 2015 21:57:04 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::,RULES_HIT:41:355:379:541:599:960:982:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1541:1593:1594:1711:1730:1747:1777:1792:2197:2199:2393:2559:2562:2693:2828:3138:3139:3140:3141:3142:3353:3622:3653:3865:3866:3867:3868:3871:3872:3873:3874:4321:4605:5007:6261:10004:10400:10471:10848:11232:11658:11914:12043:12296:12517:12519:12740:13069:13095:13161:13229:13255:13311:13357:21080,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0 X-HE-Tag: road39_77a065e7ace2a X-Filterd-Recvd-Size: 2509 Message-ID: <1432691820.2846.133.camel@perches.com> Subject: Re: [PATCH] scripts:checkpatch - Do not give error if static bool or global bool variables are assigned to false value. From: Joe Perches To: Shailendra Verma Cc: Andy Whitcroft , linux-kernel@vger.kernel.org Date: Tue, 26 May 2015 18:57:00 -0700 In-Reply-To: <1432688995-2931-1-git-send-email-shailendra.capricorn@gmail.com> References: <1432688995-2931-1-git-send-email-shailendra.capricorn@gmail.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.12.11-0ubuntu3 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1797 Lines: 50 On Wed, 2015-05-27 at 06:39 +0530, Shailendra Verma wrote: > The bool value false is not always to be 0. By definition (7.16 Boolean type and values ), false is integer 0. Setting a boolean variable to 0 is equivalent to setting it to false. What I think you mean is that a boolean variable can be set to 0 when false might be more intelligible. > So this patch will > prevent for error if static bool or global bool are initialized > with false value. [] > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl [] > # check for global initialisers. > - if ($line =~ /^\+(\s*$Type\sa*$Ident\s*(?:\s+$Modifier))*\s*=\s*(0|NULL|false)\s*;/) { > + if ($line =~ /^\+(\s*$Type\s*$Ident\s*(?:\s+$Modifier))*\s*=\s*(0|NULL)\s*;/) { > if (ERROR("GLOBAL_INITIALISERS", > "do not initialise globals to 0 or NULL\n" . > $herecurr) && I think using false adds some clarity for the reader and even if something were to be applied, the error message should probably be "do not initialize globals to $2\n" (choose the spelling of your choice for initialise/initialize) The (0|NULL|false) regex could probably be expanded to (0x0+|0|NULL|false) or that regex could be saved as a $our zero_value and tested using that new variable. [] > # check for static initialisers. > - if ($line =~ /^\+.*\bstatic\s.*=\s*(0|NULL|false)\s*;/) { > + if ($line =~ /^\+.*\bstatic\s.*=\s*(0|NULL)\s*;/) { > if (ERROR("INITIALISED_STATIC", > "do not initialise statics to 0 or NULL\n" . > $herecurr) && $1 here -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/