From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
Denis Efremov <efremov@linux.com>,
Coccinelle <cocci@systeme.lip6.fr>
Cc: Michal Marek <michal.lkml@markovi.net>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Cocci] coccinelle: api: add kvfree script
Date: Sat, 6 Jun 2020 13:21:41 +0200 [thread overview]
Message-ID: <bf698c44-4384-e471-3ff0-e38587140b98@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2006061307020.2578@hadrien>
> So there are a lot of reasons why constraints are useful.
Thanks for such a view.
Thus I dare to point the possibility out to consider their application
for mentioned function name lists (besides using SmPL disjunctions).
Can coding style concerns be resolved in a more constructive way then?
> But hiding information that could be apparent to the SmPL compiler
> and could be used to improve the performance of the matching
> process is not one of them.
Will any software extensions become possible also in this area?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
Denis Efremov <efremov@linux.com>,
Coccinelle <cocci@systeme.lip6.fr>
Cc: Michal Marek <michal.lkml@markovi.net>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: coccinelle: api: add kvfree script
Date: Sat, 06 Jun 2020 11:21:41 +0000 [thread overview]
Message-ID: <bf698c44-4384-e471-3ff0-e38587140b98@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2006061307020.2578@hadrien>
> So there are a lot of reasons why constraints are useful.
Thanks for such a view.
Thus I dare to point the possibility out to consider their application
for mentioned function name lists (besides using SmPL disjunctions).
Can coding style concerns be resolved in a more constructive way then?
> But hiding information that could be apparent to the SmPL compiler
> and could be used to improve the performance of the matching
> process is not one of them.
Will any software extensions become possible also in this area?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
Denis Efremov <efremov@linux.com>,
Coccinelle <cocci@systeme.lip6.fr>
Cc: Gilles Muller <Gilles.Muller@lip6.fr>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: coccinelle: api: add kvfree script
Date: Sat, 6 Jun 2020 13:21:41 +0200 [thread overview]
Message-ID: <bf698c44-4384-e471-3ff0-e38587140b98@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2006061307020.2578@hadrien>
> So there are a lot of reasons why constraints are useful.
Thanks for such a view.
Thus I dare to point the possibility out to consider their application
for mentioned function name lists (besides using SmPL disjunctions).
Can coding style concerns be resolved in a more constructive way then?
> But hiding information that could be apparent to the SmPL compiler
> and could be used to improve the performance of the matching
> process is not one of them.
Will any software extensions become possible also in this area?
Regards,
Markus
next prev parent reply other threads:[~2020-06-06 11:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 7:30 [Cocci] [PATCH] coccinelle: api: add kvfree script Markus Elfring
2020-06-06 7:30 ` Markus Elfring
2020-06-06 7:30 ` Markus Elfring
2020-06-06 7:46 ` [Cocci] " Julia Lawall
2020-06-06 7:46 ` Julia Lawall
2020-06-06 7:46 ` Julia Lawall
2020-06-06 9:50 ` [Cocci] " Markus Elfring
2020-06-06 9:50 ` Markus Elfring
2020-06-06 9:50 ` Markus Elfring
2020-06-07 14:02 ` [Cocci] Coccinelle: Extending capabilities for source file pre-selection Markus Elfring
2020-06-07 14:02 ` Markus Elfring
2020-06-07 14:02 ` Markus Elfring
2020-06-06 11:06 ` [Cocci] coccinelle: api: add kvfree script Markus Elfring
2020-06-06 11:06 ` Markus Elfring
2020-06-06 11:06 ` Markus Elfring
2020-06-06 11:11 ` [Cocci] " Julia Lawall
2020-06-06 11:11 ` Julia Lawall
2020-06-06 11:11 ` Julia Lawall
2020-06-06 11:21 ` Markus Elfring [this message]
2020-06-06 11:21 ` Markus Elfring
2020-06-06 11:21 ` Markus Elfring
2020-06-07 6:42 ` [Cocci] Coccinelle: Improving software components around usage of SmPL disjunctions Markus Elfring
2020-06-07 6:42 ` Markus Elfring
2020-06-07 6:42 ` Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2020-06-06 14:04 [Cocci] [PATCH] coccinelle: api: add kvfree script Markus Elfring
2020-06-06 14:04 ` Markus Elfring
2020-06-06 14:04 ` Markus Elfring
2020-06-06 14:39 ` [Cocci] " Julia Lawall
2020-06-06 14:39 ` Julia Lawall
2020-06-06 14:39 ` Julia Lawall
2020-06-06 15:10 ` [Cocci] " Markus Elfring
2020-06-06 15:10 ` Markus Elfring
2020-06-06 15:10 ` Markus Elfring
2020-06-14 15:10 [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=bf698c44-4384-e471-3ff0-e38587140b98@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=efremov@linux.com \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.