[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b362115c-6853-4047-b4c2-aad97ccf8c31@web.de>
Date: Sat, 18 Oct 2025 10:24:28 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Anand Moon <linux.amoon@...il.com>, linux-pci@...r.kernel.org,
Bjorn Helgaas <bhelgaas@...gle.com>, Kevin Xie <kevin.xie@...rfivetech.com>,
Krzysztof WilczyĆski <kwilczynski@...nel.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Manivannan Sadhasivam <mani@...nel.org>, Rob Herring <robh@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] PCI: starfive: Propagate dev_err_probe return value
> Ensure that the return value from dev_err_probe() is consistently assigned
> back to return in all error paths within starfive_pcie_clk_rst_init() and
> starfive_pcie_enable_phy() function. This ensures the original error code
> are propagation for debugging.
I find the change description improvable.
I propose to take another source code transformation approach better into account.
https://elixir.bootlin.com/linux/v6.17.1/source/drivers/base/core.c#L5031-L5075
Example:
https://elixir.bootlin.com/linux/v6.17.1/source/drivers/pci/controller/plda/pcie-starfive.c#L171-L187
ret = dev_err_probe(dev, reset_control_deassert(pcie->resets),
"failed to deassert resets\n");
if (ret)
clk_bulk_disable_unprepare(pcie->num_clks, pcie->clks);
How do you think about to achieve such a source code variant also with the help of
the semantic patch language (Coccinelle software)?
Regards,
Markus
Powered by blists - more mailing lists