All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Kahola, Mika" <mika.kahola@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Coelho, Luciano" <luciano.coelho@intel.com>
Subject: RE: [PATCH 2/2] drm/i915: use struct drm_device for clock gating funcs
Date: Tue, 25 Nov 2025 16:40:53 +0200	[thread overview]
Message-ID: <adafc80872cc09bb5698fc6e28e5d7b7a9b0e9e7@intel.com> (raw)
In-Reply-To: <DS4PPF69154114F9001C879C31796C0B8F4EFD1A@DS4PPF69154114F.namprd11.prod.outlook.com>

On Tue, 25 Nov 2025, "Kahola, Mika" <mika.kahola@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jani Nikula
>> Sent: Friday, 21 November 2025 13.22
>> To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>; Coelho, Luciano <luciano.coelho@intel.com>
>> Subject: [PATCH 2/2] drm/i915: use struct drm_device for clock gating funcs
>> 
>> While we want to refactor intel_clock_gating.[ch] and likely move a lot of display related code to display, start off with a little
>> intermediate change to use struct drm_device in the interface instead of struct drm_i915_private, to allow us to drop another
>> dependency on i915_drv.h and struct drm_i915_private.
>> 
>> Cc: Luca Coelho <luciano.coelho@intel.com>
>
> Reviewed-by: Mika Kahola <mika.kahola@intel.com>

Thanks, series pushed to din.

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-11-25 14:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 11:21 [PATCH 1/2] drm/i915/cdclk: drop i915_drv.h include Jani Nikula
2025-11-21 11:22 ` [PATCH 2/2] drm/i915: use struct drm_device for clock gating funcs Jani Nikula
2025-11-25 14:07   ` Kahola, Mika
2025-11-25 14:40     ` Jani Nikula [this message]
2025-11-21 13:46 ` [PATCH 1/2] drm/i915/cdclk: drop i915_drv.h include Kahola, Mika
2025-11-25 10:29   ` Jani Nikula
2025-11-24 20:53 ` ✓ CI.KUnit: success for series starting with [1/2] " Patchwork
2025-11-24 21:09 ` ✗ CI.checksparse: warning " Patchwork
2025-11-24 21:10 ` ✓ i915.CI.BAT: success " Patchwork
2025-11-24 21:31 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-24 23:06 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-25  2:01 ` ✗ i915.CI.Full: " 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=adafc80872cc09bb5698fc6e28e5d7b7a9b0e9e7@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=luciano.coelho@intel.com \
    --cc=mika.kahola@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.