From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: imre.deak@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH 0/3] drm/i915/display: add some sub-structs for clarity
Date: Mon, 03 Mar 2025 12:15:33 +0200 [thread overview]
Message-ID: <87o6yi1ku2.fsf@intel.com> (raw)
In-Reply-To: <cover.1740746939.git.jani.nikula@intel.com>
On Fri, 28 Feb 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> Jani Nikula (3):
> drm/i915/mst: add mst sub-struct to struct intel_dp
> drm/i915/mst: add mst sub-struct to struct intel_connector
> drm/i915/hdcp: add hdcp sub-struct to struct intel_digital_port
Thanks for the reviews, pushed to din.
BR,
Jani.
>
> drivers/gpu/drm/i915/display/g4x_dp.c | 2 +-
> drivers/gpu/drm/i915/display/g4x_hdmi.c | 2 +-
> .../gpu/drm/i915/display/intel_connector.c | 4 +-
> drivers/gpu/drm/i915/display/intel_ddi.c | 6 +-
> .../drm/i915/display/intel_display_debugfs.c | 6 +-
> .../drm/i915/display/intel_display_types.h | 44 ++---
> drivers/gpu/drm/i915/display/intel_dp.c | 38 ++---
> drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 8 +-
> drivers/gpu/drm/i915/display/intel_dp_mst.c | 154 +++++++++---------
> drivers/gpu/drm/i915/display/intel_hdcp.c | 94 +++++------
> 10 files changed, 180 insertions(+), 178 deletions(-)
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-03-03 10:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 12:49 [PATCH 0/3] drm/i915/display: add some sub-structs for clarity Jani Nikula
2025-02-28 12:49 ` [PATCH 1/3] drm/i915/mst: add mst sub-struct to struct intel_dp Jani Nikula
2025-02-28 15:52 ` Imre Deak
2025-02-28 12:49 ` [PATCH 2/3] drm/i915/mst: add mst sub-struct to struct intel_connector Jani Nikula
2025-02-28 15:52 ` Imre Deak
2025-02-28 12:49 ` [PATCH 3/3] drm/i915/hdcp: add hdcp sub-struct to struct intel_digital_port Jani Nikula
2025-02-28 15:13 ` Kandpal, Suraj
2025-02-28 14:03 ` ✓ CI.Patch_applied: success for drm/i915/display: add some sub-structs for clarity Patchwork
2025-02-28 14:03 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-28 14:04 ` ✓ CI.KUnit: success " Patchwork
2025-02-28 14:21 ` ✓ CI.Build: " Patchwork
2025-02-28 14:23 ` ✓ CI.Hooks: " Patchwork
2025-02-28 14:25 ` ✓ CI.checksparse: " Patchwork
2025-02-28 14:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-28 21:13 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-03 10:15 ` Jani Nikula [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=87o6yi1ku2.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@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