From: Julia Lawall <julia.lawall@lip6.fr>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <mmarek@suse.com>
Subject: Re: [PATCH] coccicheck: Allow for overriding spatch flags
Date: Sun, 12 Jun 2016 21:16:24 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1606122113450.2180@localhost6.localdomain6> (raw)
In-Reply-To: <1465758279-16111-1-git-send-email-deepa.kernel@gmail.com>
On Sun, 12 Jun 2016, Deepa Dinamani wrote:
> Documentation/coccinelle.txt suggests using the SPFLAGS
> make variable to pass additional options to spatch.
>
> Reorder the way SPFLAGS is added to FLAGS, to allow
> for options in the SPFLAGS to override the default
> --very-quiet option.
>
> Similarly, rearrage the FLAGS for org or report mode.
> This allows for overriding of the default --no-show-diff
> option through SPFLAGS.
The first looks like a good idea, but do you find a use case for the
second? The diff that is shown in org or report mode may be sort of
random. It is just an easy hack to reuse the same pattern code for
context, org, and report modes, but there isn't an intent to see the diff
produced by context mode in org or report mode.
thanks,
julia
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
> Cc: Julia Lawall <Julia.Lawall@lip6.fr>
> Cc: Gilles Muller <Gilles.Muller@lip6.fr>
> Cc: Nicolas Palix <nicolas.palix@imag.fr>
> Cc: Michal Marek <mmarek@suse.com>
> ---
> scripts/coccicheck | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/coccicheck b/scripts/coccicheck
> index dd85a45..f662786 100755
> --- a/scripts/coccicheck
> +++ b/scripts/coccicheck
> @@ -25,7 +25,7 @@ else
> NPROC="$J"
> fi
>
> -FLAGS="$SPFLAGS --very-quiet"
> +FLAGS="--very-quiet $SPFLAGS"
>
> # spatch only allows include directories with the syntax "-I include"
> # while gcc also allows "-Iinclude" and "-include include"
> @@ -72,7 +72,7 @@ if [ "$MODE" = "chain" ] ; then
> echo 'All available modes will be tried (in that order): patch, report, context, org'
> fi
> elif [ "$MODE" = "report" -o "$MODE" = "org" ] ; then
> - FLAGS="$FLAGS --no-show-diff"
> + FLAGS="--no-show-diff $FLAGS"
> fi
>
> if [ "$ONLINE" = "0" ] ; then
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2016-06-12 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 19:04 Deepa Dinamani
2016-06-12 19:16 ` Julia Lawall [this message]
2016-06-12 20:32 ` Deepa Dinamani
2016-06-12 20:39 ` Julia Lawall
2016-06-12 21:08 ` Deepa Dinamani
2016-06-12 21:09 ` Julia Lawall
2016-06-12 21:38 ` Nicolas Palix (LIG)
2016-06-12 21:45 ` Julia Lawall
2016-06-20 20:21 ` 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=alpine.DEB.2.02.1606122113450.2180@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®