From: joe@perches.com (Joe Perches)
To: cocci@systeme.lip6.fr
Subject: [Cocci] coccinelle: add style check for assignment in if
Date: Tue, 09 Feb 2016 15:56:47 -0800 [thread overview]
Message-ID: <1455062207.3333.6.camel@perches.com> (raw)
In-Reply-To: <56B9E1C2.7070008@users.sourceforge.net>
On Tue, 2016-02-09 at 13:55 +0100, SF Markus Elfring wrote:
> > > Would you like to consider also the reuse of SmPL variables
> > > like "org" and "report"?
> >
> > I think that there is no point for these things, because checkpatch
> > already gives warnings about this issue.
>
> Can the check result display be more convenient from the semantic
> patch script interface in comparison to the other tool?
-ENOPARSE. ?More detail please.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
Julia Lawall <julia.lawall@lip6.fr>
Cc: Kris Borer <kborer@gmail.com>, Michal Marek <mmarek@suse.com>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr
Subject: Re: coccinelle: add style check for assignment in if
Date: Tue, 09 Feb 2016 15:56:47 -0800 [thread overview]
Message-ID: <1455062207.3333.6.camel@perches.com> (raw)
In-Reply-To: <56B9E1C2.7070008@users.sourceforge.net>
On Tue, 2016-02-09 at 13:55 +0100, SF Markus Elfring wrote:
> > > Would you like to consider also the reuse of SmPL variables
> > > like "org" and "report"?
> >
> > I think that there is no point for these things, because checkpatch
> > already gives warnings about this issue.
>
> Can the check result display be more convenient from the semantic
> patch script interface in comparison to the other tool?
-ENOPARSE. More detail please.
next prev parent reply other threads:[~2016-02-09 23:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 12:46 [Cocci] [PATCH v2] coccinelle: add style check for assignment in if Kris Borer
2016-02-08 12:46 ` Kris Borer
2016-02-09 8:27 ` [Cocci] " SF Markus Elfring
2016-02-09 8:27 ` SF Markus Elfring
2016-02-09 9:18 ` [Cocci] " Julia Lawall
2016-02-09 9:18 ` Julia Lawall
2016-02-09 12:55 ` [Cocci] " SF Markus Elfring
2016-02-09 12:55 ` SF Markus Elfring
2016-02-09 23:56 ` Joe Perches [this message]
2016-02-09 23:56 ` Joe Perches
2016-02-10 9:00 ` [Cocci] " SF Markus Elfring
2016-02-10 9:00 ` SF Markus Elfring
2016-02-10 15:06 ` [Cocci] " Kris Borer
2016-02-10 15:06 ` Kris Borer
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=1455062207.3333.6.camel@perches.com \
--to=joe@perches.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 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.