All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Ville Syrjala <ville.syrjala@linux.intel.com>
Subject: [PATCH 0/3] drm/i915/display: handle hdmi connector init failures
Date: Thu, 14 Nov 2024 17:52:14 +0200	[thread overview]
Message-ID: <cover.1731599468.git.jani.nikula@intel.com> (raw)

This is an attempt to resolve [1].

BR,
Jani.


[1] https://lore.kernel.org/r/20241031105145.2140590-1-senozhatsky@chromium.org


Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Ville Syrjala <ville.syrjala@linux.intel.com>

Jani Nikula (3):
  drm/i915/hdmi: propagate errors from intel_hdmi_init_connector()
  drm/i915/hdmi: add error handling in g4x_hdmi_init()
  drm/i915/ddi: propagate errors from intel_ddi_init_hdmi_connector()

 drivers/gpu/drm/i915/display/g4x_hdmi.c   | 35 +++++++++++++++--------
 drivers/gpu/drm/i915/display/g4x_hdmi.h   |  5 ++--
 drivers/gpu/drm/i915/display/intel_ddi.c  |  6 +++-
 drivers/gpu/drm/i915/display/intel_hdmi.c | 10 ++++---
 drivers/gpu/drm/i915/display/intel_hdmi.h |  4 +--
 5 files changed, 39 insertions(+), 21 deletions(-)

-- 
2.39.5


             reply	other threads:[~2024-11-14 15:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 15:52 Jani Nikula [this message]
2024-11-14 15:52 ` [PATCH 1/3] drm/i915/hdmi: propagate errors from intel_hdmi_init_connector() Jani Nikula
2024-11-14 15:52 ` [PATCH 2/3] drm/i915/hdmi: add error handling in g4x_hdmi_init() Jani Nikula
2024-11-14 15:52 ` [PATCH 3/3] drm/i915/ddi: propagate errors from intel_ddi_init_hdmi_connector() Jani Nikula
2024-11-14 17:39 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: handle hdmi connector init failures Patchwork
2024-11-14 17:39 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-14 17:40 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-14 18:29 ` ✓ CI.Patch_applied: success " Patchwork
2024-11-14 18:30 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-14 18:31 ` ✓ CI.KUnit: success " Patchwork
2024-11-14 18:43 ` ✓ CI.Build: " Patchwork
2024-11-14 18:45 ` ✓ CI.Hooks: " Patchwork
2024-11-14 18:46 ` ✗ CI.checksparse: warning " Patchwork
2024-11-14 19:15 ` ✓ CI.BAT: success " Patchwork
2024-11-15  5:00 ` [PATCH 0/3] " Sergey Senozhatsky
2024-12-03 12:31   ` Sergey Senozhatsky
2024-12-04 15:08     ` Jani Nikula
2024-11-15 12:53 ` ✗ CI.FULL: failure for " 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=cover.1731599468.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=senozhatsky@chromium.org \
    --cc=ville.syrjala@linux.intel.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 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.