All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: <cocci@inria.fr>, Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [cocci] behavior change in semantic patches since c36b51ffc889 ("don't drop down on single statement")
Date: Fri, 7 Mar 2025 12:24:36 -0800	[thread overview]
Message-ID: <5586a98d-02dc-4b23-b439-a4b7073c2ad3@intel.com> (raw)
In-Reply-To: <d31415e8-8ab7-cac-2ba6-3ba26bb2331@inria.fr>



On 3/6/2025 4:55 PM, Julia Lawall wrote:
> 
> 
> On Thu, 6 Mar 2025, Jacob Keller wrote:
> 
>> Hi Julia,
>>
>> We use semantic patches for code cleanup regularly, and recently noticed
>> a change in behavior some some semantic patches that are run as part of
>> a build process. I've provided the patch and an explanation of my
>> discoveries thus far. Hopefully help track down whats wrong and whether
>> we need to update these patches, there is some other workaround we can
>> do, or there is actually a bug in coccinelle/spatch.
> 
> Thanks for the report, and espcially for the bisect.  I don't think it
> would be good to just revert the commit, since it is solving a real
> problem.  I will see how to get your cases working properly.
> 

Thanks :)


>>> @@
>>> expression hw, ptr;
>>> @@
>>> (
>>> - ice_free(hw, ptr);
>>> + devm_kfree(ice_hw_to_dev(hw),ptr);
>>> )
> 
> This doesn't need the starting and ending ()
> This is just a comemnt, it won't solve the problem.
> 
> julia
> 

Yep. I am honestly not sure where those came from, we've had this one
around for some time.

  reply	other threads:[~2025-03-07 20:25 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 [this message]
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
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=5586a98d-02dc-4b23-b439-a4b7073c2ad3@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=cocci@inria.fr \
    --cc=julia.lawall@inria.fr \
    --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.