From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] semantic patch feasibility
Date: Fri, 25 Apr 2014 22:52:53 +0200 [thread overview]
Message-ID: <535ACB25.8090703@users.sourceforge.net> (raw)
In-Reply-To: <CABxcv=nPEuQ0U22Lk0Pa8U=qwfLODKPGKgAoY8SKdW4L8srGoA@mail.gmail.com>
> I'm doing a kernel wide change on a core API used by a lot of drivers (~250)
> so is a lot of work to do this manually and I can miss a driver when
> grepping the code.
How do you identify your update candidates?
Have you got any specific filter pattern in mind already?
Your task will become more "interesting" if you are going to specify the
precise query on affected source files, won't it?
Regards,
Markus
next prev parent reply other threads:[~2014-04-25 20:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 12:32 [Cocci] semantic patch feasibility Javier Martinez Canillas
2014-04-25 14:30 ` SF Markus Elfring
2014-04-25 16:24 ` Julia Lawall
2014-04-25 16:31 ` SF Markus Elfring
2014-04-25 18:03 ` Julia Lawall
2014-04-25 18:50 ` Javier Martinez Canillas
2014-04-25 21:28 ` Julia Lawall
2014-04-25 22:02 ` Javier Martinez Canillas
2014-04-25 18:39 ` Javier Martinez Canillas
2014-04-25 18:33 ` Javier Martinez Canillas
2014-04-25 20:52 ` SF Markus Elfring [this message]
2014-04-25 21:30 ` Julia Lawall
2014-04-25 21:31 ` Julia Lawall
2014-04-25 16:23 ` Julia Lawall
2014-04-25 18:37 ` Javier Martinez Canillas
2014-04-25 21:25 ` Julia Lawall
2014-04-25 21:58 ` Javier Martinez Canillas
2014-04-26 5:11 ` Julia Lawall
2014-04-26 8:30 ` SF Markus Elfring
2014-04-26 14:06 ` Javier Martinez Canillas
2014-04-26 15:52 ` [Cocci] Extract an interface with SmPL SF Markus Elfring
2014-04-26 16:06 ` Julia Lawall
2014-04-26 16:31 ` Javier Martinez Canillas
2014-04-26 10:59 ` [Cocci] semantic patch feasibility Julia Lawall
2014-04-25 16:34 ` Wolfram Sang
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=535ACB25.8090703@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.