From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-renesas-soc@vger.kernel.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: [PATCH] drm: rcar-du: Use dev_err_probe()
Date: Tue, 30 May 2023 12:26:29 +0300 [thread overview]
Message-ID: <20230530092629.18329-1-laurent.pinchart+renesas@ideasonboard.com> (raw)
Replace manual handling of EPROBE_DEFER with dev_err_probe() to simplify
the code.
Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
---
drivers/gpu/drm/renesas/rcar-du/rcar_du_drv.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/renesas/rcar-du/rcar_du_drv.c b/drivers/gpu/drm/renesas/rcar-du/rcar_du_drv.c
index 1ffde19cb87f..91095f9deb8b 100644
--- a/drivers/gpu/drm/renesas/rcar-du/rcar_du_drv.c
+++ b/drivers/gpu/drm/renesas/rcar-du/rcar_du_drv.c
@@ -701,9 +701,7 @@ static int rcar_du_probe(struct platform_device *pdev)
/* DRM/KMS objects */
ret = rcar_du_modeset_init(rcdu);
if (ret < 0) {
- if (ret != -EPROBE_DEFER)
- dev_err(&pdev->dev,
- "failed to initialize DRM/KMS (%d)\n", ret);
+ dev_err_probe(&pdev->dev, ret, "failed to initialize DRM/KMS\n");
goto error;
}
base-commit: 85d712f033d23bb56a373e29465470c036532d46
prerequisite-patch-id: 74c948ef7587221bcc859d7e0b38b54b7c404163
prerequisite-patch-id: 41d31c65b9895beb2f15c1dd2b89e435657a639c
prerequisite-patch-id: bd71c64e0d7f9a6a5212ef9ad499fb7cdc718425
prerequisite-patch-id: a01de55d9563b98ab2d86d78db436da198bc4649
prerequisite-patch-id: 2faeeea13f349cae2470b09926ed52e5743f1579
prerequisite-patch-id: 783a84269c3d66600ec31046bee76e2aabcb32ad
--
Regards,
Laurent Pinchart
next reply other threads:[~2023-05-30 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 9:26 Laurent Pinchart [this message]
2023-05-30 9:38 ` [PATCH] drm: rcar-du: Use dev_err_probe() Geert Uytterhoeven
2023-05-30 9:38 ` Geert Uytterhoeven
2023-05-30 9:46 ` Laurent Pinchart
2023-05-30 9:46 ` Laurent Pinchart
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=20230530092629.18329-1-laurent.pinchart+renesas@ideasonboard.com \
--to=laurent.pinchart+renesas@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-renesas-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.