All of lore.kernel.org
 help / color / mirror / Atom feed
From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] can't match a simple line?
Date: Thu, 9 Oct 2014 15:07:00 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1410091506010.2369@hadrien> (raw)
In-Reply-To: <543685EC.6090109@redhat.com>

On Thu, 9 Oct 2014, Michael Stefaniuc wrote:

> On 10/09/2014 02:32 PM, Wolfram Sang wrote:
> > Hi,
> >
> > this is so simple yet I don't see what I do wrong?
> >
> > $ spatch --version spatch version 1.0.0-rc22 with Python support
> > and with PCRE support
> >
> > (from Debian but same with rc21):
> >
> > The rule 'test.cocci':
> >
> > @@ @@ - 	module_platform_driver(...);

Is this a normal program statement, or is it something at top level.  In
the latter case, you would need a "metavariable" declaration

declarer name module_platform_driver;

julia


> >
> > The command line:
> >
> > spatch -sp_file test.cocci drivers/i2c/muxes/
> >
> > No removals?
> >
> > init_defs_builtins: /usr/share/coccinelle/standard.h HANDLING:
> > drivers/i2c/muxes/i2c-arb-gpio-challenge.c (ONCE) Expected tokens
> > module_platform_driver
> > Skipping:drivers/i2c/muxes/i2c-mux-pca954x.c HANDLING:
> > drivers/i2c/muxes/i2c-mux-pinctrl.c HANDLING:
> > drivers/i2c/muxes/i2c-mux-gpio.c
> > Skipping:drivers/i2c/muxes/built-in.mod.c
> > Skipping:drivers/i2c/muxes/i2c-mux-pca9541.c
> >
> > It should match, or?
> Only if it can parse the blocks containing that code. What is spatch
> --parse-c saying for the affected files?
>
> bye
> 	michael
> _______________________________________________
> Cocci mailing list
> Cocci at systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
>

      reply	other threads:[~2014-10-09 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 12:32 [Cocci] can't match a simple line? Wolfram Sang
2014-10-09 12:56 ` Michael Stefaniuc
2014-10-09 13:07   ` Julia Lawall [this message]

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=alpine.DEB.2.10.1410091506010.2369@hadrien \
    --to=julia.lawall@lip6.fr \
    --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.