From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Dejin Zheng <zhengdejin5@gmail.com>, Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Checking the replacement of two specific function calls
Date: Thu, 16 Apr 2020 16:28:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2004161627300.8125@hadrien> (raw)
In-Reply-To: <735a3c61-695b-a857-b0ce-8999b04644b1@web.de>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On Thu, 16 Apr 2020, Markus Elfring wrote:
> >> Would I need any extra parameters here?
> >
> > Perhaps -I options to help it find the relevant .h file.
>
> I wonder why the relevant header files would not be found directly
> from the corresponding Git repository.
OK, it seems that the structure is defined in the same file so no include
options should be needed. But I have now lost track of what the
semantic patch actually is, so I don't know what is the problem.
julia
>
> Can a file inclusion failure become an immediate SmPL script execution error
> when a special program parameter would be passed?
>
>
> Can it be that the pointer variable “priv” to the data structure “rcar_i2c_priv”
> distracts from the desired understanding of a questionable software situation
> when the relevant declaration is provided in the same source file?
> https://elixir.bootlin.com/linux/v5.7-rc1/source/drivers/i2c/busses/i2c-rcar.c#L119
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/i2c/busses/i2c-rcar.c?id=8632e9b5645bbc2331d21d892b0d6961c1a08429#n119
>
> Regards,
> Markus
>
[-- Attachment #2: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-04-16 14:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 15:21 [Cocci] Checking the replacement of two specific function calls Markus Elfring
2020-04-15 17:52 ` Julia Lawall
2020-04-15 18:22 ` Markus Elfring
2020-04-16 7:12 ` Markus Elfring
2020-04-16 8:53 ` Julia Lawall
2020-04-16 9:11 ` Markus Elfring
2020-04-16 12:45 ` Julia Lawall
2020-04-16 14:15 ` Markus Elfring
2020-04-16 14:28 ` Julia Lawall [this message]
2020-04-17 6:08 ` Markus Elfring
2020-04-17 14:51 ` Markus Elfring
2020-04-17 18:56 ` Markus Elfring
2020-04-20 6:30 ` Markus Elfring
2020-04-16 14:30 ` Markus Elfring
2020-06-17 18:20 ` Markus Elfring
2020-04-16 12:26 ` Markus Elfring
2020-09-07 11:43 ` [Cocci] [PATCH] Coccinelle: api: Add SmPL script “use_devm_platform_get_and_ioremap_resource.cocci” Markus Elfring
2020-09-07 12:00 ` Julia Lawall
2020-09-07 13:05 ` Markus Elfring
2020-09-07 13:11 ` Julia Lawall
[not found] ` <46d314d5-822e-3d73-2d70-015794556e56@web.de>
2020-09-07 13:46 ` Julia Lawall
[not found] ` <8aaa799f-0ec4-cfd0-854a-e1006d0d200a@web.de>
2020-09-07 14:18 ` Julia Lawall
2020-09-07 16:54 ` [Cocci] [PATCH v2] " Markus Elfring
2020-09-07 17:03 ` Julia Lawall
[not found] ` <8fb7782c-538b-b657-af13-da71124e6afa@web.de>
2020-09-07 17:31 ` Julia Lawall
[not found] ` <01ea8faa-6fca-a91e-2b5d-378262dcc671@web.de>
2023-01-06 13:04 ` [cocci] [PATCH v3] " 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=alpine.DEB.2.21.2004161627300.8125@hadrien \
--to=julia.lawall@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=zhengdejin5@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).