All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Nicolas Palix <nicolas.palix@imag.fr>,
	linux-kernel@vger.kernel.org, Wen Yang <wen.yang99@zte.com.cn>,
	cocci@systeme.lip6.fr
Subject: Re: [Cocci] Coccinelle: semantic patch for missing of_node_put
Date: Fri, 17 May 2019 10:22:34 +0200	[thread overview]
Message-ID: <bb05f122-753a-7117-a00f-455b25621bac@web.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1905170912590.4014@hadrien>

> A semantic patch has no access to comments.

Thanks for your acknowledgement of the current situation.


> The only thing I can see to do is to use python to interact with some external tools.

I see more software development possibilities.

* Advanced data processing for source code comments
  https://github.com/coccinelle/coccinelle/issues/57

* Add a metavariable for the handling of source code
  https://github.com/coccinelle/coccinelle/issues/140


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@lip6.fr>
Cc: cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org,
	Gilles Muller <Gilles.Muller@lip6.fr>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Michal Marek <michal.lkml@markovi.net>,
	Nicolas Palix <nicolas.palix@imag.fr>,
	Wen Yang <wen.yang99@zte.com.cn>
Subject: Re: Coccinelle: semantic patch for missing of_node_put
Date: Fri, 17 May 2019 10:22:34 +0200	[thread overview]
Message-ID: <bb05f122-753a-7117-a00f-455b25621bac@web.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1905170912590.4014@hadrien>

> A semantic patch has no access to comments.

Thanks for your acknowledgement of the current situation.


> The only thing I can see to do is to use python to interact with some external tools.

I see more software development possibilities.

* Advanced data processing for source code comments
  https://github.com/coccinelle/coccinelle/issues/57

* Add a metavariable for the handling of source code
  https://github.com/coccinelle/coccinelle/issues/140


Regards,
Markus

  reply	other threads:[~2019-05-20 14:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201905171432571474636@zte.com.cn>
2019-05-17  7:14 ` Coccinelle: semantic patch for missing of_node_put Julia Lawall
2019-05-17  8:22   ` Markus Elfring [this message]
2019-05-17  8:22     ` Markus Elfring
2019-05-20  9:33   ` Pavel Machek
2019-05-20  9:51     ` Julia Lawall
2019-05-20  9:52     ` [Cocci] " Julia Lawall
2019-05-20  9:52       ` Julia Lawall
2019-05-20 17:20       ` [Cocci] " Sasha Levin
2019-05-20 17:20         ` Sasha Levin
2019-05-20 19:53         ` [Cocci] " Julia Lawall
2019-05-20 19:53           ` Julia Lawall
2019-05-20 20:11           ` [Cocci] " Markus Elfring
2019-05-20 20:11             ` Markus Elfring
2019-05-17  8:10 ` [Cocci] " Markus Elfring
2019-05-17  8:10   ` Markus Elfring
2019-05-18 14:43 ` [Cocci] " Markus Elfring
2019-05-18 14:43   ` Markus Elfring
2019-06-04  5:08 ` [Cocci] " Markus Elfring
2019-06-04  5:08   ` Markus Elfring
2019-06-04  5:50   ` [Cocci] " wen.yang99
2019-06-04  6:36     ` Markus Elfring
2019-06-04  6:36       ` Markus Elfring
2019-06-04  8:55       ` [Cocci] " wen.yang99
2019-06-04  9:08         ` Markus Elfring
2019-06-04  9:08           ` Markus Elfring
2019-06-04 11:28     ` [Cocci] " Markus Elfring
2019-06-04 11:28       ` Markus Elfring
2019-06-05 18:23   ` [Cocci] Coccinelle: Searching for “when done” in function comments Markus Elfring
2019-06-05 18:23     ` Markus Elfring
2019-05-09  1:47 [Cocci] [PATCH] coccinelle: semantic patch for missing of_node_put wen.yang99
2019-05-09  8:10 ` [Cocci] Coccinelle: " 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=bb05f122-753a-7117-a00f-455b25621bac@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=nicolas.palix@imag.fr \
    --cc=wen.yang99@zte.com.cn \
    /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.