[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90cea5d2-b586-6f82-34dd-d7a812f57396@web.de>
Date: Sun, 29 Sep 2019 20:00:27 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: cocci@...teme.lip6.fr, Gilles Muller <Gilles.Muller@...6.fr>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jessica Yu <jeyu@...nel.org>,
Julia Lawall <julia.lawall@...6.fr>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Matthias Maennich <maennich@...gle.com>,
Michal Marek <michal.lkml@...kovi.net>,
Nicolas Palix <nicolas.palix@...g.fr>,
Yue Haibing <yuehaibing@...wei.com>
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Martijn Coenen <maco@...roid.com>
Subject: Re: [Cocci] [RFC PATCH] scripts: Fix coccicheck failed
> Maybe the problem would be solved by putting virtual report at the top of the rule.
I assume that support for the operation mode “patch” can eventually be considered.
> But it might still fail because nothing can happen without a value
> for the virtual metavariable ns.
I imagine that the safe handling of this command line input parameter
will trigger further software development concerns.
> Should the coccinelle directory be only for things that work with make coccicheck,
I hope not.
But it seems that a filter command expressed such a restriction so far.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/coccicheck?id=02dc96ef6c25f990452c114c59d75c368a1f4c8f#n257
Is this place an update candidate now?
> or for all Coccinelle scripts?
I would prefer file storage selections in this direction.
How do you think about to improve the software taxonomy accordingly?
Regards,
Markus
Powered by blists - more mailing lists