From: Julia Lawall <julia.lawall@lip6.fr>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: nicolas.palix@univ-grenoble-alpes.fr, cocci@systeme.lip6.fr,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH] coccinelle: fix verbose message about .cocci file being run
Date: Wed, 8 Nov 2017 21:12:50 +0800 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1711082112400.2708@hadrien> (raw)
In-Reply-To: <CAK7LNARMTun58pa1Ew32SvQjR_u1Hg8mE-tDR_qqvztcx_Wnfg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
On Tue, 7 Nov 2017, Masahiro Yamada wrote:
> 2017-10-26 16:22 GMT+09:00 Nicolas Palix (LIG) <Nicolas.Palix@imag.fr>:
> > Le 26/10/17 à 06:55, Masahiro Yamada a écrit :
> >>
> >> If you run coccicheck with V=1 and COCCI=, you will see a strange
> >> path to the semantic patch file. For example, run the following:
> >>
> >> $ make V=1 COCCI=scripts/coccinelle/free/kfree.cocci coccicheck
> >> [ snip ]
> >> The semantic patch that makes this report is available
> >> in scriptcoccinelle/free/kfree.cocci.
> >>
> >> Notice "s/" was dropped from "scripts/coccinelle/free/kfree.cocci".
> >>
> >> When running coccicheck without O=, $srctree is expanded to ".", which
> >> represents one arbitrary character in the regular expression. Using
> >> sed is not a good choice here. Strip $srctree/ simply without sed.
> >>
> >> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> >
> > Acked-by: Nicolas Palix <nicolas.palix@imag.fr>
> >>
> >> ---
>
> Applied to linux-kbuild/misc.
Thanks!
julia
next prev parent reply other threads:[~2017-11-08 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 4:55 Masahiro Yamada
2017-10-26 7:22 ` Nicolas Palix (LIG)
2017-11-07 0:27 ` Masahiro Yamada
2017-11-08 13:12 ` Julia Lawall [this message]
2017-10-27 23:56 ` Jim Davis
2017-10-28 11:26 ` Masahiro Yamada
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.20.1711082112400.2708@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@univ-grenoble-alpes.fr \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®