Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp3080471pxu; Sun, 29 Nov 2020 14:34:55 -0800 (PST) X-Google-Smtp-Source: ABdhPJyoYnmntBooPJXPAWbvxfpOqEDK4GLT/mPHE1+RSDsgjx7b2v0mbzitx+NyM+6P1s74YGry X-Received: by 2002:a05:6402:d09:: with SMTP id eb9mr18570941edb.71.1606689295371; Sun, 29 Nov 2020 14:34:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606689295; cv=none; d=google.com; s=arc-20160816; b=D5mU+T/l4w6Rd3b2Yw884/pZk9ktU2ZQauuy8vyN8GcWmVwl8ztCOAKAJ+Q4mVbBwT hOeid8ATNtq3lzzPy+oaBlm0b69afQScUSIrrxj4S+70V23TJ58k+GR122LfVB2kqMfm LiTxCU+cCGAnkk/40MNpMKK8oGdwre8bn18Y1rS2GgiJbA8QuQrnN2HvjTaqKgUt0k/b gfyPiq5xgMR1AhoLFANtnnmLnc0F+/5NH0SR02Uy9hy1x25X0vLLeE3MGGyGcvjGDoK9 5n4oLC8QFIpT8tODKDtF5prt0a5Can3Lp//qi4YVhBuv7rAQTGH5i1gahokv/9GGD35Q 3LjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=KOzuptP6x6I0P7C26qoGKrHK5ZGXpwlxCkAOy9HpVis=; b=E/npQcOJHfnuzZLdMMMwr/GUXlXIt/N30C3vaAsMzXbNpy8AKByCSnrQ/sUjwSAdwl YmBo93goO19/RSNg1qwiHDNysA2E2OjTqtFpTPlQ+0cRHRDMrYDi4mFMyZ4CPvq6FnOs SIyQD4n5dppWBBYA1c4tjcrZ0vTwCmMu+hohpLaxyCzK/dgWXJhS5WhvwhhN9cVs43Mz ZO06Nbi/KeekCpgbf1WULayQOIHxpJjPIn9HwgFTuJSEt/1qqIj9HemzGUvGDXAcTRj5 6hq7P97LKfBuM5BTdq4XWzqtX3q+tnDWiaQ1C+LS9jq1yfVAbbiXVgBky+u16TiWuLrM rX7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j20si9908631edt.219.2020.11.29.14.34.32; Sun, 29 Nov 2020 14:34:55 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727798AbgK2Wcg (ORCPT + 99 others); Sun, 29 Nov 2020 17:32:36 -0500 Received: from smtprelay0038.hostedemail.com ([216.40.44.38]:54750 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726293AbgK2Wcf (ORCPT ); Sun, 29 Nov 2020 17:32:35 -0500 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay05.hostedemail.com (Postfix) with ESMTP id BCA761802926E; Sun, 29 Nov 2020 22:31:54 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,,RULES_HIT:41:355:379:599:973:988:989:1260:1277:1311:1313:1314:1345:1359:1437:1515:1516:1518:1534:1540:1593:1594:1711:1730:1747:1777:1792:2393:2559:2562:2828:2892:2898:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3871:3872:3874:4321:5007:10004:10400:10848:11026:11232:11658:11914:12048:12050:12297:12438:12740:12760:12895:13069:13161:13229:13311:13357:13439:14096:14097:14659:21080:21627:21740:30012:30029:30054:30070:30075:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: truck72_1107d5f2739c X-Filterd-Recvd-Size: 2134 Received: from XPS-9350.home (unknown [47.151.128.180]) (Authenticated sender: joe@perches.com) by omf20.hostedemail.com (Postfix) with ESMTPA; Sun, 29 Nov 2020 22:31:53 +0000 (UTC) Message-ID: <9dfe4206580f2c0d59ca0a9e510054ce378cb2d8.camel@perches.com> Subject: Re: [PATCH] locks: remove trailing semicolon in macro definition From: Joe Perches To: James Bottomley , Randy Dunlap , Tom Rix , Matthew Wilcox Cc: jlayton@kernel.org, bfields@fieldses.org, viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Date: Sun, 29 Nov 2020 14:31:51 -0800 In-Reply-To: References: <20201127190707.2844580-1-trix@redhat.com> <20201127195323.GZ4327@casper.infradead.org> <8e7c0d56-64f3-d0b6-c1cf-9f285c59f169@redhat.com> Content-Type: text/plain; charset="ISO-8859-1" User-Agent: Evolution 3.38.1-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2020-11-29 at 10:15 -0800, James Bottomley wrote: > I think nowadays we should always use static inlines for argument > checking unless we're capturing debug information like __FILE__ or > __LINE__ or something that a static inline can't. IMO: __LINE__ should never be used. __func__ is the only thing that can't be captured correctly as the inline gets its own name. __builtin_return_address(1) would generally work well enough for the inlines. > There was a time when we had problems with compiler expansion of static > inlines, so we shouldn't go back and churn the code base to change it > because there's thousands of these and possibly some old compiler used > for an obscure architecture that still needs the define. That's not a very compelling argument to me. Those old compilers and obscure architectures should continue to use the old versions of the code.