cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Marc Zyngier <maz@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Michal Marek <michal.lkml@markovi.net>,
	YueHaibing <yuehaibing@huawei.com>, Arnd Bergmann <arnd@arndb.de>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nicolas Palix <nicolas.palix@imag.fr>,
	Linus Torvalds <torvalds@linuxfoundation.org>,
	Markus Elfring <Markus.Elfring@web.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] coccinelle: api/devm_platform_ioremap_resource: remove useless script
Date: Sun, 20 Oct 2019 07:38:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1910200735400.3689@hadrien> (raw)
In-Reply-To: <868spgzcti.wl-maz@kernel.org>

> If said script was providing a correct semantic patch instead of being
> an incentive for people to churn untested patches that span the whole
> tree, that'd be a different story. But that's not what this is about.

What is the actual incorrectness with the script?

An option could be to adjust the rule such that it can be run with an
extra command line option, like -D developer but is not run by default by
make coccicheck.

thanks,
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  parent reply	other threads:[~2019-10-20  5:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e895d04ef5a282b5b48fcb21cbc175d2@www.loen.fr>
2019-10-19 11:35 ` [Cocci] coccinelle: api/devm_platform_ioremap_resource: remove useless script Markus Elfring
2019-10-19 20:43   ` Marc Zyngier
2019-10-19 22:13     ` Joe Perches
2019-10-24 15:40       ` Masahiro Yamada
2019-10-24 18:30         ` Markus Elfring
2019-10-25  8:08         ` Andy Shevchenko
2019-10-25  8:38           ` Julia Lawall
2019-10-29  2:58             ` Masahiro Yamada
2019-10-29  8:55               ` Julia Lawall
2019-10-20  5:38     ` Julia Lawall [this message]
2019-10-20  9:34       ` Marc Zyngier
2019-10-20  5:45     ` Markus Elfring
     [not found] <20191017142237.9734-1-alexandre.belloni@bootlin.com>
2019-10-19  9:00 ` [Cocci] [PATCH] " Markus Elfring
2019-10-19 12:09   ` Alexandre Belloni
2019-10-19 14:06     ` [Cocci] " Markus Elfring

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.21.1910200735400.3689@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=Markus.Elfring@web.de \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=bgolaszewski@baylibre.com \
    --cc=cocci@systeme.lip6.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=nicolas.palix@imag.fr \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linuxfoundation.org \
    --cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).