[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <821a7417-4f2a-42ed-9616-88a0c145fa5d@web.de>
Date: Sun, 6 Oct 2024 09:39:21 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Chen Ni <nichen@...as.ac.cn>, linux-rockchip@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-pci@...r.kernel.org,
Bjorn Helgaas <bhelgaas@...gle.com>, Damien Le Moal <dlemoal@...nel.org>,
Heiko Stübner <heiko@...ech.de>,
Krzysztof Wilczyński <kw@...ux.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Niklas Cassel <cassel@...nel.org>, Rob Herring <robh@...nel.org>,
Uwe Kleine-König <ukleinek@...ian.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
Cc: LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] PCI: dw-rockchip: Remove redundant dev_err()
> There is no need to call the dev_err() function directly to print a
> custom message when handling an error from platform_get_irq_byname()
> function as it is going to display an appropriate error message in case
call?
> of a failure.
Were any static source code analysis tools involved in the detection
of the presented change possibility?
By the way:
Such a patch can be generated also by the means of the semantic patch
language (Coccinelle software) for example.
Regards,
Markus
Powered by blists - more mailing lists