[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3a4c8245-9e7b-8287-90f6-b49a658fd204@web.de>
Date: Fri, 4 Oct 2019 10:23:11 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Julia Lawall <julia.lawall@...6.fr>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Matthias Männich <maennich@...gle.com>,
Michal Marek <michal.lkml@...kovi.net>,
Nicolas Palix <nicolas.palix@...g.fr>,
YueHaibing <yuehaibing@...wei.com>, Jessica Yu <jeyu@...nel.org>,
Coccinelle <cocci@...teme.lip6.fr>,
kernel-janitors@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [Cocci] [RFC] scripts: Fix coccicheck failed
>> How do you think about to avoid the addition of the SmPL variable
>> “virtual report” to the script “add_namespace.cocci” if you would dare
>> to integrate my change proposal for an adjusted directory hierarchy?
>
> Perhaps I'm lazy, but i seems simpler to add 20 characters than to move
> all of the files around...
I got concerned that you would interpret the difference statistics
of the published patches in this direction.
I propose to achieve a clear separation for SmPL scripts.
* Files which can be directly used (on their own).
* Coccicheck scripts which have got additional design requirements
for this call interface.
Which storage locations are you going to select for these variants?
Regards,
Markus
Powered by blists - more mailing lists