[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe93e337-7d8e-4b82-b187-b5a67b627544@web.de>
Date: Sun, 19 Oct 2025 18:25:27 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Anand Moon <linux.amoon@...il.com>, cocci@...ia.fr,
kernel-janitors@...r.kernel.org
Cc: linux-pci@...r.kernel.org, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, 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>
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.
Your software understanding evolved into another direction.
Can the following source code search pattern represent discussed development concerns
in a succinct way?
@display@
expression dev, e;
@@
*e = dev_err_probe(dev, e, ...)
The evaluation of such a tiny SmPL script can point out that 14 source files
of the software “Linux next-20251017” contain corresponding update candidates.
Will any adjustments become helpful also at these places?
Regards,
Markus
Powered by blists - more mailing lists