On Wed, 5 Jun 2019, Enrico Weigelt, metux IT consult wrote:
> On 05.06.19 20:52, Julia Lawall wrote:
>
> Hi,
>
> > In principle you can remove some initializations and add them back.
>
> How can I match/remote on that "#ifdef ..." ?
>
> Tried that, but got similar errors like Markus got (see hi
On 05.06.19 20:52, Julia Lawall wrote:
Hi,
In principle you can remove some initializations and add them back.
How can I match/remote on that "#ifdef ..." ?
Tried that, but got similar errors like Markus got (see his recent
mail).
It seems that spatch currently just doesn't understand prep
On Wed, 5 Jun 2019, Enrico Weigelt, metux IT consult wrote:
> Hi folks,
>
>
> is there a way to replace obsolete #ifdef's via spatch ?
>
> Here's my scenario:
>
> In the linux kernel we have many places where drivers statically assign
> pointers to match tables (eg. for oftree or acpi) into a g
On Wed, 5 Jun 2019, Enrico Weigelt, metux IT consult wrote:
> Hi folks,
>
>
> I'd like to hack up some scripts that automatically scan and report
> findings on a daily basis, eg. on the linux-next tree. Obviously,
> nobody can seriously read this all at once, especially not on a
> daily basis.
Hi folks,
I'd like to hack up some scripts that automatically scan and report
findings on a daily basis, eg. on the linux-next tree. Obviously,
nobody can seriously read this all at once, especially not on a
daily basis.
Therefore I need to:
* split the findings (eg. by ruleset or affected fil
> Just wrapping the assignment into the macro call turned out to be easy.
This feedback seems to be promising.
> But I haven't found a way to remove the now #ifdef :(
I get the following test result for a corresponding SmPL transformation
approach.
@replacement@
identifier value;
@@
-#ifdef C
ch are provided by 20 source files of
the software “Linux next-20190605”.
Will this source code analysis result trigger further development efforts
around detection of unique wordings in these descriptions?
Regards,
Markus
Hi folks,
is there a way to replace obsolete #ifdef's via spatch ?
Here's my scenario:
In the linux kernel we have many places where drivers statically assign
pointers to match tables (eg. for oftree or acpi) into a global driver
struct - sometimes this is enclosed into some #ifdef CONFIG_...,
