Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5240303yba; Mon, 13 May 2019 07:40:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqxTCNqm3/93P843VkjFjN1uPkp0ZXY49dFk0iwGoEM5nmv3TMQgcgNaC6jcDYUYnLRVJw+B X-Received: by 2002:aa7:8289:: with SMTP id s9mr33483456pfm.208.1557758409968; Mon, 13 May 2019 07:40:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557758409; cv=none; d=google.com; s=arc-20160816; b=J+5Y3LvphApNvtinSkmo3BiawBnz8twPM4W+FW0x3fqxsA5Dq+2p9MHWkCicDjDtoU QVEnx2E+a7EfgEGqTm07iSMXYMGxuZOZZrDaZ2CPu4uyX/pwPvNfCJ6AI2gRTiB9BCg+ YOtdPCKz5EEwx2osYj6fh+weWM8CtMZpk2Y5903d2tj+oLlFbEJNMlMGnPsefjM4E+r8 IhTj+YD1XANBG/RbCq5b/UKj4+2gGnGvmd2aWElHzZdzpZOazbUPgxj0Z7qG9gX9BN/K uoFP6HSu0bGHF2tArUhPmnb6mF7XZM6Rox1XcAgvw1zFQ3a2WGwhzTSAekPD73lQ6VSG vHZQ== 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=vLkJjXpNQtd8QOM9qkJ1D7M363IwYzsi4df96+Vk4o4=; b=HcIWYDWa+eMnzzq2AYun81YIS2s0vQa9abj5PMFMa1azRYXPsJRen2jCDIICnoJdli OozkjA+ecN9SUeoX+t6/1yswIJ6gE/c/s9Xs4GU/qFavzW8H4oBngbL6j6oN/RpVT9Bv lkeRclh8un1FV0amhKKQv1Ey4l70puGttJfvXGS/cNtNiU2Pxq1WT0aVh5/D4YY0f1I9 RssIXHlET2FLNkukSwW/r1HCbqujlolPF/1aXRUo3d/UuO0AcK3doQR1jgJ/3u44j9C5 EvJSwUlvZMeu6wbuA3QFz/rAxjY5P9YWik7mvJioDOhqRpNebn/vB4rIVyNFQCexd9v6 xgdg== 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 m10si16284645pgp.478.2019.05.13.07.39.53; Mon, 13 May 2019 07:40:09 -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 S1728878AbfEMLvr (ORCPT + 99 others); Mon, 13 May 2019 07:51:47 -0400 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:52931 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727690AbfEMLvr (ORCPT ); Mon, 13 May 2019 07:51:47 -0400 X-IronPort-AV: E=Sophos;i="5.60,465,1549926000"; d="scan'208";a="305811236" Received: from vaio-julia.rsr.lip6.fr ([132.227.76.33]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 May 2019 13:51:44 +0200 Date: Mon, 13 May 2019 13:51:39 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: Markus Elfring cc: Gilles Muller , Masahiro Yamada , Michal Marek , Nicolas Palix , Wen Yang , cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org, Yi Wang Subject: Re: [3/5] Coccinelle: put_device: Merge four SmPL when constraints into one In-Reply-To: <1c36d747-ac2d-0187-ddb7-d1a2bb18ddaf@web.de> Message-ID: References: <1553321671-27749-1-git-send-email-wen.yang99@zte.com.cn> <6b62ecb5-ab88-22d9-eee2-db4f58b6d2ae@web.de> <1c36d747-ac2d-0187-ddb7-d1a2bb18ddaf@web.de> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 13 May 2019, Markus Elfring wrote: > >> An assignment target was repeated in four SmPL when constraints. > >> Combine the exclusion specifications into disjunctions for the semantic > >> patch language so that this target is referenced only once there. > > > > NACK. > > I find this rejection questionable. > > > > This exceeds 80 characters > > The line became 105 characters long. > 14 space characters can eventually be omitted. > > > > and provides no readability benefit. > > I try to stress SmPL functionality in this use case. That's not the goal of the semantic patches in the kernel. The rule is fine as it is. > >> +++ b/scripts/coccinelle/free/put_device.cocci > >> @@ -23,10 +23,7 @@ if (id == NULL || ...) { ... return ...; } > >> when != platform_device_put(id) > >> when != of_dev_put(id) > >> when != if (id) { ... put_device(&id->dev) ... } > >> - when != e1 = (T)id > >> - when != e1 = (T)(&id->dev) > >> - when != e1 = get_device(&id->dev) > >> - when != e1 = (T1)platform_get_drvdata(id) > >> + when != e1 = \( (T) \( id \| (&id->dev) \) \| get_device(&id->dev) \| (T1)platform_get_drvdata(id) \) > > How do you think about to extend the Coccinelle software in the way > that such a detailed constraint can be specified on separate lines > (without duplicated SmPL code)? This causes some ambiguities in the parser. No change is likely to occur here. julia > > How long will it take to reconsider corresponding software limitations? > > Regards, > Markus >