From: Andrzej Hajda <a.hajda@samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Andrzej Hajda <a.hajda@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <mmarek@suse.com>,
cocci@systeme.lip6.fr (moderated list:COCCINELLE/Semantic
Patches (SmPL))
Subject: [PATCH v2] Coccinelle: fix incorrect -include option transformation
Date: Tue, 22 Sep 2015 15:15:30 +0200 [thread overview]
Message-ID: <1442927730-18676-1-git-send-email-a.hajda@samsung.com> (raw)
In-Reply-To: <56015315.507@samsung.com>
kbuild/gcc uses -include option to include files and -I to provide paths for
#include <> directive. In case of spatch latter option should be prefixed with
two -.
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
---
scripts/coccicheck | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/coccicheck b/scripts/coccicheck
index bbf901a..b2d75818 100755
--- a/scripts/coccicheck
+++ b/scripts/coccicheck
@@ -30,7 +30,7 @@ FLAGS="$SPFLAGS --very-quiet"
# spatch only allows include directories with the syntax "-I include"
# while gcc also allows "-Iinclude" and "-include include"
COCCIINCLUDE=${LINUXINCLUDE//-I/-I }
-COCCIINCLUDE=${COCCIINCLUDE//-include/-I}
+COCCIINCLUDE=${COCCIINCLUDE// -include/ --include}
if [ "$C" = "1" -o "$C" = "2" ]; then
ONLINE=1
--
1.9.1
next prev parent reply other threads:[~2015-09-22 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 12:48 [PATCH] Coccinelle: remove " Andrzej Hajda
2015-09-22 12:58 ` Julia Lawall
2015-09-22 13:09 ` Andrzej Hajda
2015-09-22 13:15 ` Andrzej Hajda [this message]
2015-09-22 13:27 ` [PATCH v2] Coccinelle: fix " Julia Lawall
2015-10-26 20:34 ` Michal Marek
2015-09-22 13:23 ` [PATCH] Coccinelle: remove " Julia Lawall
2015-09-22 13:00 ` Julia Lawall
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=1442927730-18676-1-git-send-email-a.hajda@samsung.com \
--to=a.hajda@samsung.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=b.zolnierkie@samsung.com \
--cc=cocci@systeme.lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.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
all inboxes | Powered by JetHome®