Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/4] drm/i915: move display info related stuff under display/
Date: Wed, 04 Oct 2023 13:44:14 +0300	[thread overview]
Message-ID: <874jj6fz0h.fsf@intel.com> (raw)
In-Reply-To: <ZRxyJE3p15e1CBph@intel.com>

On Tue, 03 Oct 2023, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, Oct 03, 2023 at 03:42:06PM +0300, Jani Nikula wrote:
>> Continue separation of display code from the rest.
>> 
>> Jani Nikula (4):
>>   drm/i915: convert INTEL_DISPLAY_ENABLED() into a function
>>   drm/i915: move display info related macros to display
>>   drm/i915: separate display runtime info init
>>   drm/i915: separate subplatform init and runtime feature init
>
> Didn't spot anything wrong. I was a bit suspicious about
> deferring the port_mask mangling, but doesn't look like we
> need it that early anywhere.
>
> Series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Thanks, pushed to din.

>
>> 
>>  drivers/gpu/drm/i915/display/intel_crt.c      |  2 +-
>>  .../drm/i915/display/intel_display_device.c   | 43 ++++++++++++++++++-
>>  .../drm/i915/display/intel_display_device.h   | 10 +++++
>>  drivers/gpu/drm/i915/display/intel_dp.c       |  2 +-
>>  drivers/gpu/drm/i915/display/intel_dp_mst.c   |  2 +-
>>  drivers/gpu/drm/i915/display/intel_dvo.c      |  2 +-
>>  drivers/gpu/drm/i915/display/intel_hdmi.c     |  2 +-
>>  drivers/gpu/drm/i915/display/intel_hotplug.c  |  2 +-
>>  drivers/gpu/drm/i915/display/intel_panel.c    |  2 +-
>>  drivers/gpu/drm/i915/display/intel_sdvo.c     |  2 +-
>>  drivers/gpu/drm/i915/display/intel_tv.c       |  2 +-
>>  drivers/gpu/drm/i915/i915_driver.c            |  1 +
>>  drivers/gpu/drm/i915/i915_drv.h               | 14 ------
>>  drivers/gpu/drm/i915/intel_device_info.c      | 22 ----------
>>  14 files changed, 62 insertions(+), 46 deletions(-)
>> 
>> -- 
>> 2.39.2

-- 
Jani Nikula, Intel

      reply	other threads:[~2023-10-04 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 12:42 [Intel-gfx] [PATCH 0/4] drm/i915: move display info related stuff under display/ Jani Nikula
2023-10-03 12:42 ` [Intel-gfx] [PATCH 1/4] drm/i915: convert INTEL_DISPLAY_ENABLED() into a function Jani Nikula
2023-10-03 12:42 ` [Intel-gfx] [PATCH 2/4] drm/i915: move display info related macros to display Jani Nikula
2023-10-03 12:42 ` [Intel-gfx] [PATCH 3/4] drm/i915: separate display runtime info init Jani Nikula
2023-10-03 12:42 ` [Intel-gfx] [PATCH 4/4] drm/i915: separate subplatform init and runtime feature init Jani Nikula
2023-10-03 15:06 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: move display info related stuff under display/ Patchwork
2023-10-03 15:06 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-03 15:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-03 19:25 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-03 19:57 ` [Intel-gfx] [PATCH 0/4] " Ville Syrjälä
2023-10-04 10:44   ` 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=874jj6fz0h.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox