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
Subject: Re: [PATCH 0/3] drm/i915/pin: refactor to i915 core
Date: Tue, 07 Apr 2026 21:58:46 +0300 [thread overview]
Message-ID: <c6374e5cd248c0ebf1f020a374ec32580880f8c7@intel.com> (raw)
In-Reply-To: <adTcMdEqCRyjTPzK@intel.com>
On Tue, 07 Apr 2026, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, Apr 07, 2026 at 01:04:34PM +0300, Jani Nikula wrote:
>> 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.
>
> Looks all right to me. I have the same file rename somewhere in my
> current branch, and I think eg. the runtime pm thing I still have
> mixed in with some other changes. So I can rebase easily on top of
> these and shrink my branch a little bit.
>
> Series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks, pushed to din.
> And speaking of my branch, I think it should be fairly close to
> being done. I still need to think what to do about
> restore.pending_fb_pin, and some commits may still need further
> splitting. And proper commit messages need to be written of
> course.
\o/
>
> That said, the whole thing is rather big and I've not smoke tested
> it even once, so I might still need to fix a boatload of bugs...
>
>>
>> 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
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-04-07 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:04 [PATCH 0/3] drm/i915/pin: refactor to i915 core Jani Nikula
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 [this message]
2026-04-07 10:50 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-04-07 11:01 ` ✓ i915.CI.BAT: " Patchwork
2026-04-07 11:49 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-07 14:24 ` ✗ 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=c6374e5cd248c0ebf1f020a374ec32580880f8c7@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 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.