From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Xichao Zhao <zhao.xichao@vivo.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: rt2x00: Remove the use of dev_err_probe()
Date: Fri, 22 Aug 2025 09:44:50 +0200 [thread overview]
Message-ID: <20250822074450.GB46129@wp.pl> (raw)
In-Reply-To: <20250820085843.397945-1-zhao.xichao@vivo.com>
Hi
On Wed, Aug 20, 2025 at 04:58:43PM +0800, Xichao Zhao wrote:
> The dev_err_probe() doesn't do anything when error is '-ENOMEM'.
> Therefore, remove the useless call to dev_err_probe(), and just
> return the value instead.
There is this comment regarding dev_err_probe:
* Using this helper in your probe function is totally fine even if @err
* is known to never be -EPROBE_DEFER.
* The benefit compared to a normal dev_err() is the standardized format
* of the error code, which is emitted symbolically (i.e. you get "EAGAIN"
* instead of "-35"), and having the error code returned allows more
* compact error paths.
If you want this change you have please justify it better, i.e.
we don't need to print error message because ...
Regards
Stanislaw
> Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
> ---
> drivers/net/wireless/ralink/rt2x00/rt2800soc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/ralink/rt2x00/rt2800soc.c b/drivers/net/wireless/ralink/rt2x00/rt2800soc.c
> index 8f510a84e7f1..e5c99fc6509b 100644
> --- a/drivers/net/wireless/ralink/rt2x00/rt2800soc.c
> +++ b/drivers/net/wireless/ralink/rt2x00/rt2800soc.c
> @@ -289,7 +289,7 @@ static int rt2x00soc_probe(struct platform_device *pdev, const struct rt2x00_ops
>
> hw = ieee80211_alloc_hw(sizeof(struct rt2x00_dev), ops->hw);
> if (!hw)
> - return dev_err_probe(&pdev->dev, -ENOMEM, "Failed to allocate hardware");
> + return -ENOMEM;
>
> platform_set_drvdata(pdev, hw);
>
> --
> 2.34.1
>
prev parent reply other threads:[~2025-08-22 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 8:58 Xichao Zhao
2025-08-22 7:44 ` Stanislaw Gruszka [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=20250822074450.GB46129@wp.pl \
--to=stf_xl@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zhao.xichao@vivo.com \
/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®