From: Markus Elfring <Markus.Elfring@web.de>
To: Jacob Keller <jacob.e.keller@intel.com>, cocci@inria.fr
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [cocci] behavior change in semantic patches since c36b51ffc889 …
Date: Sat, 8 Mar 2025 10:07:34 +0100 [thread overview]
Message-ID: <fdf1c4b6-9f0d-4c27-a668-65cc5926ab3d@web.de> (raw)
In-Reply-To: <8bc6d266-cc33-4f77-93d8-b12f2086449e@intel.com>
> For what its worth, I was finally able to get things working pretty much
> the same as before with the following semantic patches:
This is a nice feedback.
>> @@
>> expression hw;
>> @@
>> -ice_free
>> +devm_kfree
>> (
>> +ice_hw_to_dev(
>> hw
>> +)
>> , ...)
Did you observe that the omission of a semicolon at the end
triggered desirable effects?
> and
>
>> @disable drop_cast@
>> void * void_ptr;
>> type T;
>> @@
>> -(T *)void_ptr
>> +void_ptr
Would another SmPL code variant be occasionally helpful?
-(T *)
void_ptr
Are there cases to consider where casts should be preserved?
Regards,
Markus
next prev parent reply other threads:[~2025-03-08 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 0:43 [cocci] behavior change in semantic patches since c36b51ffc889 ("don't drop down on single statement") Jacob Keller
2025-03-07 0:55 ` Julia Lawall
2025-03-07 20:24 ` Jacob Keller
2025-03-07 10:47 ` [cocci] behavior change in semantic patches since c36b51ffc889 … Markus Elfring
2025-03-07 20:53 ` Jacob Keller
2025-03-07 22:47 ` Jacob Keller
2025-03-08 9:07 ` Markus Elfring [this message]
2025-03-10 18:34 ` Jacob Keller
2025-03-11 9:10 ` Markus Elfring
2025-03-08 8:39 ` Markus Elfring
2025-03-10 18:27 ` Jacob Keller
2025-03-11 9:26 ` Przemek Kitszel
2025-03-08 9:45 ` [cocci] Evolution of transformation processes? Markus Elfring
2025-03-10 18:23 ` Jacob Keller
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=fdf1c4b6-9f0d-4c27-a668-65cc5926ab3d@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=jacob.e.keller@intel.com \
--cc=przemyslaw.kitszel@intel.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 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.