From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Elfring Date: Sun, 17 Feb 2019 12:20:51 +0000 Subject: Re: [v6] coccinelle: semantic code search for missing put_device() Message-Id: <10836645-5b19-a748-56d7-c0572a76ab4d@web.de> List-Id: References: <8e7ba7c0-b7fe-a1f0-d28b-0c716ecbcfdb@web.de> <1c152067-0135-79d7-1285-4bb9925054c8@web.de> <782fd1c3-80ff-a296-b3a2-351257bb13b3@web.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: Julia Lawall , Wen Yang Cc: Michal Marek , kernel-janitors@vger.kernel.org, Nicolas Palix , LKML , Coccinelle , Cheng Shengyu , Wen Yang >> If you would insist on the specification of such an assignment exclusion >> for a SmPL ellipsis: >> Can we agree on a correct order? > > I don't get your point. I propose to take another closer look at a bit of SmPL code. > There is no correct order. I have got an other software development view here. > Each order expresses something different. I agree to this information. > The order that is currently in the semantic patch is the one > that is more likely in practice. Please check once more. … +@search exists@ +local idexpression id; +expression x,e,e1; +position p1,p2; … +@@ + +id = of_find_device_by_node@p1(x) +... when != e = id … Or: … + ... when != id = e … Which SmPL specification will achieve the desired software behaviour? Regards, Markus