[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b39e1a7d-1505-4f26-aa6c-c18a151be8ab@web.de>
Date: Sat, 18 Oct 2025 13:40:45 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Anand Moon <linux.amoon@...il.com>, cocci@...ia.fr,
linux-pci@...r.kernel.org, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Krzysztof WilczyĆski <kwilczynski@...nel.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Manivannan Sadhasivam <mani@...nel.org>, Rob Herring <robh@...nel.org>,
Siddharth Vadapalli <s-vadapalli@...com>,
Vignesh Raghavendra <vigneshr@...com>, LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [1/3] PCI: j721e: Propagate dev_err_probe return value
>> How do you think about to achieve such a source code variant also with the help of
>> the semantic patch language (Coccinelle software)?
> I do not have any idea about this.
Can another source code search pattern (like the following) trigger further
development considerations?
@display@
expression dev, e, x;
@@
if (e)
{
... when != e = x
* dev_err_probe(dev, e, ...);
...
}
Regards,
Markus
Powered by blists - more mailing lists