Coccinelle Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mmarek@suse.com (Michal Marek)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH] Coccinelle: pm_runtime: ensure relevance of pm_runtime reports
Date: Sat, 1 Oct 2016 23:04:07 +0200	[thread overview]
Message-ID: <57F024C7.7050503@suse.com> (raw)
In-Reply-To: <1474532935-22506-1-git-send-email-Julia.Lawall@lip6.fr>

Dne 22.9.2016 v 10:28 Julia Lawall napsal(a):
> pm_runtime.cocci starts with one rule that searches for a variety of
> functions calls, followed by various rules that report errors.  Previously,
> the only connection between the first rule and the rest was to check that
> the first rule had matched somewhere.  Change the rules to propagate a
> position from the first rule to the others, to make sure that the sites
> reported on are the same as the sites that were identified as having the
> relevant functions.
> 
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>

Applied to kbuild.git#misc.

Thanks,
Michal

      reply	other threads:[~2016-10-01 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  8:28 [Cocci] [PATCH] Coccinelle: pm_runtime: ensure relevance of pm_runtime reports Julia Lawall
2016-10-01 21:04 ` Michal Marek [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=57F024C7.7050503@suse.com \
    --to=mmarek@suse.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