From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Maud Spierings via B4 Relay
<devnull+maudspierings.gocontroll.com@kernel.org>
Cc: Vincent Mailhol <mailhol@kernel.org>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
Maud Spierings <maudspierings@gocontroll.com>
Subject: Re: [PATCH] net: can: mcp251x: use dev_err_probe() in probe
Date: Fri, 31 Oct 2025 13:17:38 +0100 [thread overview]
Message-ID: <20251031-lumpy-fierce-sturgeon-01885c-mkl@pengutronix.de> (raw)
In-Reply-To: <20251030-mcp_err-v1-1-eecf737823b7@gocontroll.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On 30.10.2025 08:07:42, Maud Spierings via B4 Relay wrote:
> From: Maud Spierings <maudspierings@gocontroll.com>
>
> The currently used combination of dev_err plus return leaves a loud
> error in dmesg even when the error is a deferred probe which gets
> resolved later. For example a supply that has not been probed yet.
>
> Use dev_err_probe to improve the handling/display of errors.
>
> Signed-off-by: Maud Spierings <maudspierings@gocontroll.com>
Applied to linux-can-next.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-11-02 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 7:07 [PATCH] net: can: mcp251x: use dev_err_probe() in probe Maud Spierings via B4 Relay
2025-10-31 12:17 ` Marc Kleine-Budde [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=20251031-lumpy-fierce-sturgeon-01885c-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=devnull+maudspierings.gocontroll.com@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=maudspierings@gocontroll.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;
as well as URLs for NNTP newsgroup(s).