Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Grzelak" <michal.grzelak@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 1/4] drm/i915: remove unused dev_priv local variable
Date: Mon, 22 Dec 2025 14:28:23 +0100 (CET)	[thread overview]
Message-ID: <07291b73-9a3b-b5ef-d5c1-cd2048f61ee9@intel.com> (raw)
In-Reply-To: <222871a73efbe1049862d11a03abf253611e46b1.1766406794.git.jani.nikula@intel.com>

[-- Attachment #1: Type: text/plain, Size: 360 bytes --]

On Mon, 22 Dec 2025, Jani Nikula wrote:
> Since commit 35ec71285c93 ("drm/i915/pc8: Add parent interface for PC8
> forcewake tricks"), the __maybe_unused dev_priv has become definitely
> unused. Remove, along with the i915_drv.h include.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

Reviewed-by: Michał Grzelak <michal.grzelak@intel.com>

BR,
Michał

  reply	other threads:[~2025-12-22 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22 12:33 [PATCH v2 0/4] drm/i915/display: reduce i915_drv.h usage Jani Nikula
2025-12-22 12:34 ` [PATCH v2 1/4] drm/i915: remove unused dev_priv local variable Jani Nikula
2025-12-22 13:28   ` Michał Grzelak [this message]
2025-12-22 12:34 ` [PATCH v2 2/4] drm/xe/compat: remove unused forcewake get/put macros Jani Nikula
2025-12-22 13:29   ` Michał Grzelak
2025-12-22 12:34 ` [PATCH v2 3/4] drm/xe/compat: convert uncore macro to static inlines Jani Nikula
2025-12-22 13:31   ` Michał Grzelak
2025-12-22 12:34 ` [PATCH v2 4/4] drm/i915/display: use to_intel_uncore() to avoid i915_drv.h Jani Nikula
2025-12-22 13:32   ` Michał Grzelak
2025-12-22 21:20 ` ✗ CI.checkpatch: warning for drm/i915/display: reduce i915_drv.h usage (rev2) Patchwork
2025-12-22 21:22 ` ✓ CI.KUnit: success " Patchwork
2025-12-22 21:37 ` ✗ CI.checksparse: warning " Patchwork
2025-12-22 22:14 ` ✓ Xe.CI.BAT: success " Patchwork
2025-12-23  5:10 ` ✗ Xe.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=07291b73-9a3b-b5ef-d5c1-cd2048f61ee9@intel.com \
    --to=michal.grzelak@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