From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Doug Anderson <dianders@chromium.org>
Cc: <broonie@kernel.org>, <akashast@codeaurora.org>,
<vkoul@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 3/3] spi: geni-qcom: Use devm functions to simplify code
Date: Fri, 13 Sep 2024 14:44:29 +0800 [thread overview]
Message-ID: <10e77c5a-a188-698b-0c82-86c4bcdf114d@huawei.com> (raw)
In-Reply-To: <CAD=FV=U+kc1rKSDDo-Zx+CiuapoJ8izrCW0Wh-PfR7ivY_4bXw@mail.gmail.com>
On 2024/9/12 21:38, Doug Anderson wrote:
> Hi,
>
> On Wed, Sep 11, 2024 at 8:53 PM Jinjie Ruan <ruanjinjie@huawei.com> wrote:
>>
>>>> @@ -1132,6 +1134,12 @@ static int spi_geni_probe(struct platform_device *pdev)
>>>> if (ret)
>>>> return ret;
>>>>
>>>> + ret = devm_add_action_or_reset(dev, spi_geni_release_dma_chan, mas);
>>>> + if (ret) {
>>>> + dev_err(dev, "Unable to add action.\n");
>>>> + return ret;
>>>> + }
>>>
>>> Use dev_err_probe() to simplify.
>>>
>>> ret = devm_add_action_or_reset(dev, spi_geni_release_dma_chan, mas);
>>> if (ret)
>>> return dev_err_probe(dev, ret, "Unable to add action.\n");
>>
>> It seems that if it only return -ENOMEM or 0, using dev_err_probe() has
>> not not much value for many community maintainers.
>
> While I won't insist, it still has some value to use dev_err_probe()
> as I talked about in commit 7065f92255bb ("driver core: Clarify that
> dev_err_probe() is OK even w/out -EPROBE_DEFER")
The main difference is that when use dev_err_probe(),there will print
anything on -ENOMEM now.
>
> -Doug
next prev parent reply other threads:[~2024-09-13 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 13:28 [PATCH v4 0/3] spi: geni-qcom: Undo runtime PM changes at driver exit time Jinjie Ruan
2024-09-09 13:28 ` [PATCH v4 1/3] " Jinjie Ruan
2024-09-09 13:28 ` [PATCH v4 2/3] spi: geni-qcom: Fix incorrect free_irq() sequence Jinjie Ruan
2024-09-09 13:28 ` [PATCH v4 3/3] spi: geni-qcom: Use devm functions to simplify code Jinjie Ruan
2024-09-11 22:53 ` Doug Anderson
2024-09-12 3:53 ` Jinjie Ruan
2024-09-12 13:38 ` Doug Anderson
2024-09-13 6:44 ` Jinjie Ruan [this message]
2024-09-13 16:27 ` Doug Anderson
2024-09-14 1:17 ` Jinjie Ruan
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=10e77c5a-a188-698b-0c82-86c4bcdf114d@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=akashast@codeaurora.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=vkoul@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