public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Nishanth Menon <nm@ti.com>,
	<"ukleinek@kernel.org  u.kleine-koenig"@pengutronix.de>
Cc: <ssantosh@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <krzk@kernel.org>,
	<jic23@kernel.org>
Subject: Re: [PATCH -next v2 2/4] soc: ti: knav_dma: Use dev_err_probe() to simplfy code
Date: Sat, 31 Aug 2024 09:59:33 +0800	[thread overview]
Message-ID: <29edea69-92ce-2ac9-2aa8-bb9a4674ca01@huawei.com> (raw)
In-Reply-To: <20240830103155.5vs2hdokw6yysq47@finance>



On 2024/8/30 18:31, Nishanth Menon wrote:
> On 14:32-20240830, Jinjie Ruan wrote:
>> Use the dev_err_probe() helper to simplify error handling
>> during probe.
>>
>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
>> ---
>> v2:
>> - Split into 2 patches.
>> ---
>>  drivers/soc/ti/knav_dma.c | 12 ++++--------
>>  1 file changed, 4 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/soc/ti/knav_dma.c b/drivers/soc/ti/knav_dma.c
>> index 15e41d3a5e22..eeec422a46f0 100644
>> --- a/drivers/soc/ti/knav_dma.c
>> +++ b/drivers/soc/ti/knav_dma.c
>> @@ -708,17 +708,13 @@ static int knav_dma_probe(struct platform_device *pdev)
>>  	struct device_node *node = pdev->dev.of_node;
>>  	int ret = 0;
>>  
>> -	if (!node) {
>> -		dev_err(&pdev->dev, "could not find device info\n");
>> -		return -EINVAL;
>> -	}
>> +	if (!node)
>> +		return dev_err_probe(&pdev->dev, -EINVAL, "could not find device info\n");
>>  
>>  	kdev = devm_kzalloc(dev,
>>  			sizeof(struct knav_dma_pool_device), GFP_KERNEL);
>> -	if (!kdev) {
>> -		dev_err(dev, "could not allocate driver mem\n");
>> -		return -ENOMEM;
>> -	}
>> +	if (!kdev)
>> +		return dev_err_probe(dev, -ENOMEM, "could not allocate driver mem\n");
> 
> These make no sense to me :( -> just using dev_err_probe when there is
> no chance of -EPROBE_DEFER ?

I noticed a change in dev_err_probe() this year, which is described in
this patch:

For an out-of-memory error there should be no additional output. Adapt
dev_err_probe() to not emit the error message when err is -ENOMEM.
This simplifies handling errors that might among others be -ENOMEM.


And the comment of dev_err_probe() said below:

* Using this helper in your probe function is totally fine even if @err
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
is
~~
 * known to never be -EPROBE_DEFER.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

https://lore.kernel.org/all/3d1e308d45cddf67749522ca42d83f5b4f0b9634.1718311756.git.u.kleine-koenig@baylibre.com/
> 
>>  
>>  	kdev->dev = dev;
>>  	INIT_LIST_HEAD(&kdev->list);
>> -- 
>> 2.34.1
>>
> 

  parent reply	other threads:[~2024-08-31  1:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30  6:32 [PATCH -next v2 0/4] soc: ti: Simplify with scoped for each OF child loop and dev_err_probe() Jinjie Ruan
2024-08-30  6:32 ` [PATCH -next v2 1/4] soc: ti: knav_dma: Simplify with scoped for each OF child loop Jinjie Ruan
2024-08-30  6:32 ` [PATCH -next v2 2/4] soc: ti: knav_dma: Use dev_err_probe() to simplfy code Jinjie Ruan
2024-08-30 10:31   ` Nishanth Menon
2024-08-30 10:36     ` Krzysztof Kozlowski
2024-08-30 10:42       ` Krzysztof Kozlowski
2024-08-31  1:59     ` Jinjie Ruan [this message]
2024-08-31  5:21       ` Krzysztof Kozlowski
2024-08-31  6:27         ` Jinjie Ruan
2024-08-31 18:53           ` Andrew Lunn
2024-09-03 13:40       ` Uwe Kleine-König
2024-08-30  6:32 ` [PATCH -next v2 3/4] soc: ti: knav_qmss_queue: Simplify with scoped for each OF child loop Jinjie Ruan
2024-08-30  6:32 ` [PATCH -next v2 4/4] soc: ti: knav_qmss_queue: Simplify with dev_err_probe() Jinjie Ruan
2024-08-30 10:38   ` Nishanth Menon
2024-08-31 11:06   ` Krzysztof Kozlowski

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=29edea69-92ce-2ac9-2aa8-bb9a4674ca01@huawei.com \
    --to=ruanjinjie@huawei.com \
    --cc="ukleinek@kernel.org  u.kleine-koenig"@pengutronix.de \
    --cc=jic23@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=ssantosh@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