From: Michal Marek <mmarek@suse.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: "Nicolas Palix (LIG)" <Nicolas.Palix@imag.fr>,
Deepa Dinamani <deepa.kernel@gmail.com>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Gilles Muller <Gilles.Muller@lip6.fr>
Subject: Re: [PATCH] coccicheck: Allow for overriding spatch flags
Date: Mon, 20 Jun 2016 22:21:38 +0200 [thread overview]
Message-ID: <20160620202137.GA13127@sepie.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.02.1606122345410.2180@localhost6.localdomain6>
On Sun, Jun 12, 2016 at 11:45:57PM +0200, Julia Lawall wrote:
>
>
> On Sun, 12 Jun 2016, Nicolas Palix (LIG) wrote:
>
> > Le 12/06/16 à 21:04, Deepa Dinamani a écrit :
> > > 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.
> > >
> > > 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>
> > Acked-By: Nicolas Palix <nicolas.palix@imag.fr>
>
> Acked-by: Julia Lawall <julia.lawall@lip6.fr>
Applied to kbuild.git#misc.
Michal
prev parent reply other threads:[~2016-06-20 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 19:04 [PATCH] coccicheck: Allow for overriding spatch flags Deepa Dinamani
2016-06-12 19:16 ` Julia Lawall
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 [this message]
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=20160620202137.GA13127@sepie.suse.cz \
--to=mmarek@suse.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Nicolas.Palix@imag.fr \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).