From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
uma.shankar@intel.com
Subject: Re: [PATCH 5/8] drm/i915/dram: convert to struct intel_display
Date: Thu, 13 Nov 2025 15:45:51 +0200 [thread overview]
Message-ID: <e4f348f5d56fbd015b682ff90c15c93e35a5cba3@intel.com> (raw)
In-Reply-To: <aRXfqt3OMWs6emKW@intel.com>
On Thu, 13 Nov 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> I was wondering if we have any situations here where the display
> vs. graphics ver differs, but can't immediately think of anything
> that would go wrong here. So seems fine.
Ditto. Fingers crossed. ;)
> I think we should land https://patchwork.freedesktop.org/series/156793/
> before this one though, just in case we late discover that we need
> a stable backport of it.
Ack.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-11-13 13:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 9:57 [PATCH 0/8] drm/i915: start dissolving soc/ Jani Nikula
2025-11-13 9:57 ` [PATCH 1/8] drm/i915/edram: extract i915_edram.[ch] for edram detection Jani Nikula
2025-11-13 9:57 ` [PATCH 2/8] drm/i915: split out i915_freq.[ch] Jani Nikula
2025-11-13 9:58 ` [PATCH 3/8] drm/i915: move intel_dram.[ch] from soc/ to display/ Jani Nikula
2025-11-13 9:58 ` [PATCH 4/8] drm/xe: remove MISSING_CASE() from compat i915_utils.h Jani Nikula
2025-11-13 9:58 ` [PATCH 5/8] drm/i915/dram: convert to struct intel_display Jani Nikula
2025-11-13 13:39 ` Ville Syrjälä
2025-11-13 13:45 ` Jani Nikula [this message]
2025-11-13 9:58 ` [PATCH 6/8] drm/i915: move dram_info " Jani Nikula
2025-11-13 9:58 ` [PATCH 7/8] drm/i915: move intel_rom.[ch] from soc/ to display/ Jani Nikula
2025-11-13 9:58 ` [PATCH 8/8] drm/xe: remove remaining platform checks from compat i915_drv.h Jani Nikula
2025-11-13 10:06 ` ✗ CI.checkpatch: warning for drm/i915: start dissolving soc/ Patchwork
2025-11-13 10:08 ` ✓ CI.KUnit: success " Patchwork
2025-11-13 10:30 ` ✗ CI.checksparse: warning " Patchwork
2025-11-13 11:15 ` ✓ Xe.CI.BAT: success " Patchwork
2025-11-13 13:29 ` [PATCH 0/8] " Jani Nikula
2025-11-13 13:44 ` Jani Nikula
2025-11-13 13:37 ` [PATCH] drm/i915/gmch: split out i915_gmch.[ch] from soc Jani Nikula
2025-11-13 13:37 ` [PATCH] drm/i915: move intel_gmch.[ch] from soc/ to display/ Jani Nikula
2025-11-13 13:53 ` Ville Syrjälä
2025-11-13 15:22 ` Jani Nikula
2025-11-13 13:37 ` [PATCH] drm/i915/gmch: convert intel_gmch.c to struct intel_display Jani Nikula
2025-11-13 13:38 ` [PATCH] drm/i915/gmch: find bridge device locally Jani Nikula
2025-11-13 15:08 ` Ville Syrjälä
2025-11-13 15:26 ` Jani Nikula
2025-11-13 13:38 ` [PATCH] drm/xe: use the same vga decode code as i915 Jani Nikula
2025-11-14 22:23 ` kernel test robot
2025-11-13 15:45 ` ✗ Xe.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=e4f348f5d56fbd015b682ff90c15c93e35a5cba3@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=uma.shankar@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).