From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Markus Elfring <Markus.Elfring@web.de>,
<linux-ide@vger.kernel.org>, Damien Le Moal <dlemoal@kernel.org>,
Niklas Cassel <cassel@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ata: pata_octeon_cf: Use common error handling code in octeon_cf_probe()
Date: Wed, 18 Sep 2024 15:35:14 +0300 [thread overview]
Message-ID: <f45d5e6d-ab82-f86b-8afc-414e7c1fd28f@omp.ru> (raw)
In-Reply-To: <abe87c03-3a73-3f16-92eb-a988a61649d5@omp.ru>
On 9/17/24 23:44, Sergey Shtylyov wrote:
[...]
>>> From: Markus Elfring <elfring@users.sourceforge.net>
>>> Date: Tue, 17 Sep 2024 13:43:24 +0200
>>>
>>> Add a label so that a bit of exception handling can be better reused
>>
>> s/exception/error/.
>>
>>> in a subsequent if branch of this function implementation.
>>>
>>> This issue was detected by using the Coccinelle software.
>>>
>>> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
>>> ---
>>> drivers/ata/pata_octeon_cf.c | 9 ++++-----
>>> 1 file changed, 4 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/ata/pata_octeon_cf.c b/drivers/ata/pata_octeon_cf.c
>>> index 0bb9607e7348..62289f6aef95 100644
>>> --- a/drivers/ata/pata_octeon_cf.c
>>> +++ b/drivers/ata/pata_octeon_cf.c
>>> @@ -848,14 +848,13 @@ static int octeon_cf_probe(struct platform_device *pdev)
>>> struct resource *res_dma;
>>> int i;
>>> res_dma = platform_get_resource(dma_dev, IORESOURCE_MEM, 0);
>>> - if (!res_dma) {
>>> - put_device(&dma_dev->dev);
>>> - of_node_put(dma_node);
>>> - return -EINVAL;
>>> - }
>>> + if (!res_dma)
>>> + goto put_device;
>>> +
>>> cf_port->dma_base = (u64)devm_ioremap(&pdev->dev, res_dma->start,
>>> resource_size(res_dma));
>>> if (!cf_port->dma_base) {
>>> +put_device:
>>
>> Ugh... :-/
>> Please use the new-fangled *devm_platform_ioremap_resource() instead of those
Ugh, s/*//...
>> old-fashioned APIs.
>
> Another option is to place this error patch somewhere at the end
s/patch/path/, of course... :-)
> of this function but I think I prefer the new APIs.
[...]
MBR, Sergey
prev parent reply other threads:[~2024-09-18 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 11:50 Markus Elfring
2024-09-17 17:43 ` Sergey Shtylyov
2024-09-17 20:44 ` Sergey Shtylyov
2024-09-18 12:35 ` Sergey Shtylyov [this message]
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=f45d5e6d-ab82-f86b-8afc-414e7c1fd28f@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=Markus.Elfring@web.de \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®