From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Ville Syrjala <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH v2 0/5] drm/i915/display: handle hdmi connector init failures, and no HDMI/DP cases
Date: Thu, 5 Dec 2024 12:53:26 +0900 [thread overview]
Message-ID: <20241205035326.GD16709@google.com> (raw)
In-Reply-To: <cover.1733324735.git.jani.nikula@intel.com>
On (24/12/04 17:07), Jani Nikula wrote:
>
> v2 of [1] attempting to resolve [2].
Works like a charm!
Tested-by: Sergey Senozhatsky <senozhatsky@chromium.org>
prev parent reply other threads:[~2024-12-05 3:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:07 [PATCH v2 0/5] drm/i915/display: handle hdmi connector init failures, and no HDMI/DP cases Jani Nikula
2024-12-04 15:07 ` [PATCH v2 1/5] drm/i915/hdmi: propagate errors from intel_hdmi_init_connector() Jani Nikula
2024-12-04 15:07 ` [PATCH v2 2/5] drm/i915/hdmi: add error handling in g4x_hdmi_init() Jani Nikula
2024-12-04 15:07 ` [PATCH v2 3/5] drm/i915/ddi: propagate errors from intel_ddi_init_hdmi_connector() Jani Nikula
2024-12-04 15:07 ` [PATCH v2 4/5] drm/i915/display: add intel_encoder_is_hdmi() Jani Nikula
2024-12-05 3:44 ` Kandpal, Suraj
2024-12-04 15:07 ` [PATCH v2 5/5] drm/i915/ddi: only call shutdown hooks for valid encoders Jani Nikula
2024-12-05 3:52 ` Kandpal, Suraj
2024-12-04 15:39 ` ✓ CI.Patch_applied: success for drm/i915/display: handle hdmi connector init failures, and no HDMI/DP cases Patchwork
2024-12-04 15:39 ` ✓ CI.checkpatch: " Patchwork
2024-12-04 15:40 ` ✓ CI.KUnit: " Patchwork
2024-12-04 15:58 ` ✓ CI.Build: " Patchwork
2024-12-04 16:00 ` ✓ CI.Hooks: " Patchwork
2024-12-04 16:02 ` ✗ CI.checksparse: warning " Patchwork
2024-12-04 16:23 ` ✓ Xe.CI.BAT: success " Patchwork
2024-12-05 3:53 ` Sergey Senozhatsky [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=20241205035326.GD16709@google.com \
--to=senozhatsky@chromium.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--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 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).