[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a840e22a-0152-6aa2-e626-33011ef4afe0@web.de>
Date: Mon, 30 Mar 2020 12:15:52 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Julia Lawall <julia.lawall@...ia.fr>,
Michel Lespinasse <walken@...gle.com>,
Coccinelle <cocci@...teme.lip6.fr>, linux-mm@...ck.org
Cc: Davidlohr Bueso <dave@...olabs.net>,
Peter Zijlstra <peterz@...radead.org>,
Hugh Dickins <hughd@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
Liam Howlett <Liam.Howlett@...cle.com>,
Jason Gunthorpe <jgg@...pe.ca>,
Matthew Wilcox <willy@...radead.org>,
Ying Han <yinghan@...gle.com>,
David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Laurent Dufour <ldufour@...ux.ibm.com>,
Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [Cocci] [v3 05/10] mmap locking API: Improving the Coccinelle
software
>> …
>> (ONCE) CPP-MACRO: found known macro = FNAME
>> …
>> parse error
…
>> How would you like to improve the affected software areas?
>
> This can be addressed by adding a macro definition to standard.h.
A corresponding specification is used already.
https://github.com/coccinelle/coccinelle/blob/fdf0b68ddd0a518cc6ca64f063bc74ed54e29a7b/standard.h#L508
> But once the change is done, I don't see any reason to bother with this.
How will the support evolve for data processing around the application
of similar macros?
Regards,
Markus
Powered by blists - more mailing lists