All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Clarification for dependencies in SmPL rules
Date: Sun, 24 Aug 2014 15:00:30 +0200	[thread overview]
Message-ID: <53F9E1EE.10002@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1408240751210.2460@hadrien>

> Maybe it would be more efficient.  But conceptually it is redundant.

Thanks for your feedback.

I would find it a bit clearer or safer to use a SmPL variable like "r.i" only if
a corresponding dependency was specified on the rule beginning.

Regards,
Markus

  reply	other threads:[~2014-08-24 13:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23  5:34 [Cocci] =?y?q?=5BPATCH=20v2=5D=20coccinelle=3A=20misc=3A=20semantic=20patch=20to=20delete=20overly=20complex=20return=20code=20processing?= Julia Lawall
2014-08-23  5:34 ` =?y?q?=5BPATCH=20v2=5D=20coccinelle=3A=20misc=3A=20semantic=20patch=20to=20delete=20overly=20complex=20return=20code=20processing?= Julia Lawall
2014-08-23  5:34 ` =?y?q?=5BPATCH=20v2=5D=20coccinelle=3A=20misc=3A=20semantic=20patch=20to=20delete=20overly=20complex Julia Lawall
2014-08-24 12:41 ` [Cocci] Clarification for dependencies in SmPL rules SF Markus Elfring
2014-08-24 12:51   ` Julia Lawall
2014-08-24 13:00     ` SF Markus Elfring [this message]
2014-08-24 13:19       ` Julia Lawall
2014-08-24 13:30         ` SF Markus Elfring
2014-09-26 11:43 ` [Cocci] [PATCH v2] coccinelle: misc: semantic patch to delete overly complex return code processing Michal Marek
2014-09-26 11:43   ` Michal Marek
2014-09-26 11:43   ` Michal Marek

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=53F9E1EE.10002@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.