From: michael.opdenacker@free-electrons.com (Michael Opdenacker)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Coccinelle rules for module_pci_driver
Date: Thu, 16 Oct 2014 21:26:10 +0200 [thread overview]
Message-ID: <54401BD2.9050209@free-electrons.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1410161554230.2585@hadrien>
Hi Julia,
On 10/16/2014 03:56 PM, Julia Lawall wrote:
> I suggest the following semantic patch. It is in two parts. The first
> part matches all of the functions/declarations to ensure that they are all
> present. The second part then makes the transformation.
>
> I get a change in only one file.
Many thanks for this new version (interesting approach that has the
advantage of being progressive and repeatable) and for your explanations.
I confirm that it works for me and that I will work on making it
suitable for "make coccicheck" in the Linux kernel.
Cheers,
Michael.
--
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098
next prev parent reply other threads:[~2014-10-16 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 12:13 [Cocci] Coccinelle rules for module_pci_driver Michael Opdenacker
2014-10-16 13:33 ` Julia Lawall
2014-10-16 13:56 ` Julia Lawall
2014-10-16 19:26 ` Michael Opdenacker [this message]
2014-10-16 19:28 ` Julia Lawall
Reply instructions:
You may reply publicly 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54401BD2.9050209@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--cc=cocci@systeme.lip6.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox