From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH 0/3] drm/i915/pin: refactor to i915 core
Date: Tue, 7 Apr 2026 13:04:34 +0300 [thread overview]
Message-ID: <cover.1775556190.git.jani.nikula@intel.com> (raw)
Something I started last week before Ville said he'd look into the whole
pin stuff. If this is helpful, let's merge, but if it's in the way, it
was pretty quick and can be thrown away.
BR,
Jani.
Jani Nikula (3):
drm/i915: move intel_fb_pin.c to i915_fb_pin.c
drm/i915/pin: s/dev_priv/i915/ and drop struct drm_device usage
drm/i915/pin: switch to i915 core runtime pm
drivers/gpu/drm/i915/Makefile | 2 +-
.../{display/intel_fb_pin.c => i915_fb_pin.c} | 44 +++++++++----------
2 files changed, 22 insertions(+), 24 deletions(-)
rename drivers/gpu/drm/i915/{display/intel_fb_pin.c => i915_fb_pin.c} (90%)
--
2.47.3
next reply other threads:[~2026-04-07 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:04 Jani Nikula [this message]
2026-04-07 10:04 ` [PATCH 1/3] drm/i915: move intel_fb_pin.c to i915_fb_pin.c Jani Nikula
2026-04-08 2:55 ` Kandpal, Suraj
2026-04-07 10:04 ` [PATCH 2/3] drm/i915/pin: s/dev_priv/i915/ and drop struct drm_device usage Jani Nikula
2026-04-07 10:04 ` [PATCH 3/3] drm/i915/pin: switch to i915 core runtime pm Jani Nikula
2026-04-07 10:11 ` ✗ CI.checkpatch: warning for drm/i915/pin: refactor to i915 core Patchwork
2026-04-07 10:12 ` ✓ CI.KUnit: success " Patchwork
2026-04-07 10:28 ` [PATCH 0/3] " Ville Syrjälä
2026-04-07 18:58 ` Jani Nikula
2026-04-07 10:50 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-04-07 11:49 ` ✗ 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=cover.1775556190.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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