From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH 0/1] Return -EPROBE_DEFER from xe_display_driver_probe_defer()
Date: Wed, 6 Sep 2023 17:00:48 -0300 [thread overview]
Message-ID: <20230906200049.49674-1-gustavo.sousa@intel.com> (raw)
The function xe_display_driver_probe_defer() is supposed to return
-EPROBE_DEFER when not yet ready to continue the probing, but the
current implementation is actually returning 1 instead of the proper
value, which would probably keep the probe operation to be attempted
again. Fix that by returning the expected value in case we need to defer
the probe.
Gustavo Sousa (1):
fixup! drm/xe/display: Implement display support
drivers/gpu/drm/xe/xe_display.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.41.0
next reply other threads:[~2023-09-06 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 20:00 Gustavo Sousa [this message]
2023-09-06 20:00 ` [Intel-xe] [PATCH 1/1] fixup! drm/xe/display: Implement display support Gustavo Sousa
2023-09-06 20:49 ` Lucas De Marchi
2023-09-06 21:26 ` Gustavo Sousa
2023-09-06 20:56 ` [Intel-xe] ✓ CI.Patch_applied: success for Return -EPROBE_DEFER from xe_display_driver_probe_defer() Patchwork
2023-09-06 20:56 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-06 20:57 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-06 21:04 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-06 21:04 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-06 21:06 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-07 20:06 ` [Intel-xe] ✓ CI.Patch_applied: success for Return -EPROBE_DEFER from xe_display_driver_probe_defer() (rev2) Patchwork
2023-09-07 20:07 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-07 20:08 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-07 20:15 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-07 20:15 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-07 20:16 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-07 20:48 ` [Intel-xe] ✓ CI.BAT: " Patchwork
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=20230906200049.49674-1-gustavo.sousa@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.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