Coccinelle archive on
 help / color / Atom feed
From: Markus Elfring <>
To: Julia Lawall <>, Coccinelle <>
Cc: Kate Stewart <>,
	Yi Wang <>,
	Michal Marek <>,
	Greg Kroah-Hartman <>,
	Nicolas Palix <>,
	LKML <>,
	Thomas Gleixner <>,
	Wen Yang <>,
	Allison Randal <>
Subject: Re: [Cocci] Coccinelle: pci_free_consistent: Checking when constraints
Date: Mon, 9 Sep 2019 12:40:46 +0200
Message-ID: <> (raw)
In-Reply-To: <alpine.DEB.2.21.1909082149100.2644@hadrien>

>> I just try again to clarify if the specification of a single function call
>> exclusion can (and should) be sufficient also at this place.
> It's not sufficient.
> I explained why it's not sufficient.

Thanks for another bit of information.

> If you had made your change and tested it, it's at least highly probable
> that you would understand why it is not sufficient as well.
> You first reflex when you have a question should be to try what you are
> wondering about, not to head for the mailing list.

I got the impression that a few of our previous clarification attempts
pointed design possibilities out into other directions.

* Coccinelle: semantic patch for missing of_node_put
  Response by Wen Yang
  17 May 2019 14:32:57 +0800 (CST)

* [v5] Coccinelle: semantic code search for missing put_device()
  Discussion contribution by Markus Elfring

> Please stop spreading misinformation.

I find the provided software documentation still incomplete.
Thus I hope also that the situation can be improved by additional communication.

See also:
  [v5] Coccinelle: semantic code search for missing put_device()
  Response by Julia Lawall
  16 Feb 2019 10:36:45 +0100 (CET)

How will the software development attention evolve further around the safe handling
of code exclusion specifications together with the semantic patch language?

Cocci mailing list

  parent reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08  8:10 Markus Elfring
2019-09-08  8:23 ` Julia Lawall
2019-09-08 12:48   ` Markus Elfring
     [not found]     ` <alpine.DEB.2.21.1909082149100.2644@hadrien>
2019-09-09 10:40       ` Markus Elfring [this message]
2019-09-16  6:24       ` Markus Elfring

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Coccinelle archive on

Archives are clonable:
	git clone --mirror cocci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 cocci cocci/ \
	public-inbox-index cocci

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox