Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1263379pxk; Fri, 25 Sep 2020 10:08:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyjb7l1asLZGcGadmjGDbBjOn6oSaxYklvtLvZzXwmQj/oi+v7u6raCOu8t6VCy9GFUxf9q X-Received: by 2002:a17:906:b146:: with SMTP id bt6mr3573843ejb.287.1601053701938; Fri, 25 Sep 2020 10:08:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601053701; cv=none; d=google.com; s=arc-20160816; b=V1K0PnhKnrsEWl4XTFbHdVcVEy1luLfwwdiD6xw4RKoddGXNUXnZRdV6KSy24iESH8 1puUIkV/EzjwTVj57EfmSjJnpIU9f8PPVh/xHUYAbiO1NeV7+CcNvkdtBMU63DVaNhK+ OtZEMJNS8oysA7CjOLAmqNLL+hVf0xf8pC95kj21L7lwaVn6VREeZa3KslChdax1m/TK GahRCpzhb8MsZQlsr6DLnUPrerDba7SQElnHTO2S08KI/Fm8QKRjsaYQvIrTk1AkM0eu 3grOITA6KqOm84wC0v+XREZuuPSDChJdD3MkMdLe5ERZ7tNZHTin7mc7O7sUOcDpZFdg vMCg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date; bh=YurMyAz2YYEuKmoC6T7xmrba6bsko6D67DqAfRxio54=; b=vJ2OvBdzDLne7PiCkC4b5nvqAKCy+Xvp8GrhfSBGaSjWPmcGq4jbAkVnBvUR27hhxn lXwoluctxD97ybZ6LXlDNrQkJbneDGLAPkS/H6bn+xj1h/U+xRxo7e6ihbzzlMYddHfv TYV0qRdNv/qnNe4B9J5pGZmHR6B/y5nV7Kz7PQWhKSgYBF5oiVC1R/xDwPjsDFD/Fj6Q G06f7g0vz8bdSzOKc9wDIQ9HI+iJWsUsGtO8Bo6YxXy0Tq74VO1voJL3EVhuxDFgydZe l0+fSzJ+hgowuTm9Oks21bU1LLsCNVQ7JXzLGE0rfViATgxQy26Nn04KSW25+D6f0yGs quRg== 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 lv10si2296065ejb.539.2020.09.25.10.07.41; Fri, 25 Sep 2020 10:08:21 -0700 (PDT) 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 S1729121AbgIYRGa (ORCPT + 99 others); Fri, 25 Sep 2020 13:06:30 -0400 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:53315 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727812AbgIYRGa (ORCPT ); Fri, 25 Sep 2020 13:06:30 -0400 X-IronPort-AV: E=Sophos;i="5.77,302,1596492000"; d="scan'208";a="360082879" Received: from abo-173-121-68.mrs.modulonet.fr (HELO hadrien) ([85.68.121.173]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Sep 2020 19:06:21 +0200 Date: Fri, 25 Sep 2020 19:06:20 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: Joe Perches cc: Thomas Gleixner , =?UTF-8?Q?Valdis_Kl=C4=93tnieks?= , kernel-janitors , kernelnewbies , linux-kernel-mentees@lists.linuxfoundation.org, Andrew Morton , cocci , Giuseppe Scrivano , LKML , Andy Whitcroft Subject: Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon) In-Reply-To: Message-ID: References: <87r1qqvo2d.fsf@nanos.tec.linutronix.de> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 24 Sep 2020, Joe Perches wrote: > On Thu, 2020-09-24 at 23:53 +0200, Thomas Gleixner wrote: > > On Thu, Sep 24 2020 at 13:33, Joe Perches wrote: > > > On Thu, 2020-09-24 at 22:19 +0200, Thomas Gleixner wrote: > > > > On Sat, Aug 22 2020 at 09:07, Julia Lawall wrote: > > > > > On Fri, 21 Aug 2020, Joe Perches wrote: > > > > > > True enough for a general statement, though the coccinelle > > > > > > script Julia provided does not change a single instance of > > > > > > for loop expressions with commas. > > > > > > > > > > > > As far as I can tell, no logic defect is introduced by the > > > > > > script at all. > > > > > > > > > > The script has a rule to ensure that what is changed is part of a top > > > > > level statement that has the form e1, e2;. I put that in to avoid > > > > > transforming cases where the comma is the body of a macro, but it protects > > > > > against for loop headers as well. > > > > > > > > Right. I went through the lot and did not find something dodgy. Except > > > > for two hunks this still applies. Can someone please send a proper patch > > > > with changelog/SOB etc. for this? > > > > > > Treewide? > > > > > > Somebody no doubt would complain, but there > > > _really should_ be some mechanism for these > > > trivial and correct treewide changes... > > > > There are lots of mechanisms: > > I've tried them all. > > None of them work particularly well, > especially the individual patch route. > > > - Andrew picks such changes up > > Generally not treewide. > > > - With a few competent eyeballs on it (reviewers) this can go thorugh > > the trivial tree as well. It's more than obvious after all. > > Jiri is almost non-existent when it comes to > trivial treewide patches. > > > - Send the script to Linus with a proper change log attached and ask > > him to run it. > > Linus has concerns about backports and what he > deems trivialities. Generally overblown IMO. > > > - In the worst case if nobody feels responsible, I'll take care. > > If Julia doesn't send a new patch in the next few > days, I will do the apply, fixup and resend of hers. > > So, you're on-deck, nearly up... > > > All of the above is better than trying to get the attention of a > > gazillion of maintainters. > > True. > > And all of the treewide changes depend on some > generic acceptance of value in the type of change. > > Some believe that comma->semicolon conversions > aren't useful as there isn't a logical change and > the compiler output wouldn't be different. I have a script that will cut up the patches and send them to the appropriate maintainers, so I have no problem with that route. julia