From: Imre Deak <imre.deak@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 0/6] drm/i915/display: power conversion to struct intel_display
Date: Fri, 29 Nov 2024 16:18:18 +0200 [thread overview]
Message-ID: <Z0nNKuZpvT0sEeiF@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <cover.1732808222.git.jani.nikula@intel.com>
On Thu, Nov 28, 2024 at 05:38:18PM +0200, Jani Nikula wrote:
> This is v2 of [1] with patch 1 dropped, and some minor checkpatch issues
> fixed.
>
> [1] https://lore.kernel.org/r/cover.1732727056.git.jani.nikula@intel.com
The patchset looks ok:
Reviewed-by: Imre Deak <imre.deak@intel.com>
>
> Jani Nikula (6):
> drm/i915/display: convert for_each_power_well() to struct
> intel_display
> drm/i915/display: convert for_each_power_domain_well() to struct
> intel_display
> drm/i915/display: convert power wells to struct intel_display
> drm/i915/display: convert power domain code internally to struct
> intel_display
> drm/i915/display: convert high level power interfaces to struct
> intel_display
> drm/i915/display: convert power map to struct intel_display
>
> .../drm/i915/display/intel_display_debugfs.c | 3 +-
> .../drm/i915/display/intel_display_driver.c | 8 +-
> .../gpu/drm/i915/display/intel_display_irq.c | 3 +-
> .../drm/i915/display/intel_display_power.c | 948 +++++++++---------
> .../drm/i915/display/intel_display_power.h | 31 +-
> .../i915/display/intel_display_power_map.c | 56 +-
> .../i915/display/intel_display_power_well.c | 548 +++++-----
> .../i915/display/intel_display_power_well.h | 35 +-
> drivers/gpu/drm/i915/display/intel_dpio_phy.c | 7 +-
> drivers/gpu/drm/i915/display/intel_hdcp.c | 2 +-
> .../drm/i915/display/intel_modeset_setup.c | 2 +-
> drivers/gpu/drm/i915/display/intel_pps.c | 4 +-
> drivers/gpu/drm/i915/display/intel_psr.c | 6 +-
> drivers/gpu/drm/i915/i915_driver.c | 32 +-
> drivers/gpu/drm/xe/display/xe_display.c | 28 +-
> 15 files changed, 870 insertions(+), 843 deletions(-)
>
> --
> 2.39.5
>
next prev parent reply other threads:[~2024-11-29 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 15:38 [PATCH v2 0/6] drm/i915/display: power conversion to struct intel_display Jani Nikula
2024-11-28 15:38 ` [PATCH v2 1/6] drm/i915/display: convert for_each_power_well() " Jani Nikula
2024-11-28 15:38 ` [PATCH v2 2/6] drm/i915/display: convert for_each_power_domain_well() " Jani Nikula
2024-11-28 15:38 ` [PATCH v2 3/6] drm/i915/display: convert power wells " Jani Nikula
2024-11-28 15:38 ` [PATCH v2 4/6] drm/i915/display: convert power domain code internally " Jani Nikula
2024-11-29 14:17 ` Imre Deak
2024-11-29 14:46 ` Jani Nikula
2024-11-28 15:38 ` [PATCH v2 5/6] drm/i915/display: convert high level power interfaces " Jani Nikula
2024-11-28 15:38 ` [PATCH v2 6/6] drm/i915/display: convert power map " Jani Nikula
2024-11-28 18:13 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: power conversion to struct intel_display (rev2) Patchwork
2024-11-28 18:13 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-28 18:22 ` ✗ i915.CI.BAT: failure " Patchwork
2024-11-29 8:19 ` Jani Nikula
2024-11-29 16:08 ` Illipilli, TejasreeX
2024-11-29 14:00 ` ✓ i915.CI.BAT: success " Patchwork
2024-11-29 14:18 ` Imre Deak [this message]
2024-11-29 19:12 ` ✗ i915.CI.Full: failure " 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=Z0nNKuZpvT0sEeiF@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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