Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp3170016ybd; Fri, 28 Jun 2019 04:08:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqwGWEGqYg8Q2BoP2gXbH8xgpYQXXnVnWMPmb3zvnWnDR9MEvlIlyj9vcFMMY1bZAidSBEGM X-Received: by 2002:a63:5444:: with SMTP id e4mr8116069pgm.451.1561720097326; Fri, 28 Jun 2019 04:08:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561720097; cv=none; d=google.com; s=arc-20160816; b=SEQ8WHfxxThb6qO3erFrM8GInG+5EFg0g3A52GXEwlvUVAZ3n9loOX5c8BRyzMSsN+ LYjgvAmGN0yjFjCjeLG6mDXS/e73rHpAtdVNIDMMo+exsC9qrqN74aWV8wXG2J70naTR 6QpYSlNTiikiORD/I5cimnIM8WVr0FFGb6XDwHaUXjN6nxr6u0cwnGlAm06+6NjTqUq2 qPCETau4W7nUd6J2oa2+tu6bXjX5/JhAd7h/CbNcR9C0bDWgynBZTYvlA9zP4sC72hC1 S2gHKjZYEeY035qd5dq8M6N3AAyqxpjimHLu29qxx52zMa2hjFTwsDF5AOekO55kh56r oQ+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=tBX0gBCS17RXser+H+YS9JaU8J9gIMuVXHKeFoV03vw=; b=0m5AELWiM7Qj1iFuxofO+k+Nii1s71N8Wz85tQsgsAzw5pwxqJY9K6E7D+Q1SvobUb O37hCxJrz/DfFKby1X5IETKqjQKhOPI9ZF1DD1UUfPp2O9iy3Lboeq7g3OMHYXpWZHoy YV9N6NwhtkRJrZKS1C8VwYvsCR0taOOpAalIvJJiZ1Rhq341X+aWSSaq87VNAoBcYylZ GtW++2e5jBZeDzOcFZsVKwDeQNbJyEd4vtwJMuYYyC+tE2LUW9rb69S6N19w/oGDncwQ NvM3m8Sj0d1UhQ3W1JZpglzWmmhEJIxgBtzWCFD2x0qzkCvFYLKhgDwbNoI10BpjRPkl 6rAQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g23si2069599pfi.153.2019.06.28.04.08.00; Fri, 28 Jun 2019 04:08:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726656AbfF1LHy (ORCPT + 99 others); Fri, 28 Jun 2019 07:07:54 -0400 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:39257 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726514AbfF1LHx (ORCPT ); Fri, 28 Jun 2019 07:07:53 -0400 X-IronPort-AV: E=Sophos;i="5.63,427,1557180000"; d="scan'208";a="311767956" Received: from wifi-eduroam-85-160.paris.inria.fr ([128.93.85.160]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Jun 2019 13:07:51 +0200 Date: Fri, 28 Jun 2019 13:07:51 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: Markus Elfring cc: Wen Yang , linux-kernel@vger.kernel.org, Yi Wang , Gilles Muller , Nicolas Palix , Michal Marek , Masahiro Yamada , cocci@systeme.lip6.fr Subject: Re: [PATCH v2] coccinelle: semantic code search for missing of_node_put In-Reply-To: <904b9362-cd01-ffc9-600b-0c48848617a0@web.de> Message-ID: References: <1561690732-20694-1-git-send-email-wen.yang99@zte.com.cn> <904b9362-cd01-ffc9-600b-0c48848617a0@web.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-202224278-1561720071=:2538" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-202224278-1561720071=:2538 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT > > +x = @p1\(of_find_all_nodes\| > > I would find this SmPL disjunction easier to read without the usage > of extra backslashes. > > +x = > +(of_… > +|of_… > +)@p1(...); Did you actually test this? I doubt that a position metavariable can be put on a ) of a disjunction. > > +| > > +return x; > > +| > > +return of_fwnode_handle(x); > > Can a nested SmPL disjunction be helpful at such places? > > +|return > +(x > +|of_fwnode_handle(x) > +); The original code is much more readable. The internal representation will be the same. > > + when != v4l2_async_notifier_add_fwnode_subdev(<...x...>) > > Would the specification variant “<+... x ...+>” be relevant > for the parameter selection? I'm indeed quite surprised that <...x...> would be accepted by the parser. julia --8323329-202224278-1561720071=:2538--