From: Jani Nikula <jani.nikula@intel.com>
To: "Hogander, Jouni" <jouni.hogander@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/7] drm/i915/gem: relocate __i915_gem_object_{flush, invalidate}_frontbuffer()
Date: Wed, 11 Mar 2026 12:12:05 +0200 [thread overview]
Message-ID: <f6e185b82149d2af71077605a47344f2114b6a27@intel.com> (raw)
In-Reply-To: <846e0fde752600f4f8232713f13816d4f17a5dc2.camel@intel.com>
On Wed, 04 Mar 2026, "Hogander, Jouni" <jouni.hogander@intel.com> wrote:
> On Mon, 2026-03-02 at 20:17 +0200, Jani Nikula wrote:
>> Move __i915_gem_object_{flush,invalidate}_frontbuffer() to
>> i915_gem_object_frontbuffer.c. All the other i915 gem object
>> frontbuffer
>> functions are there already, and the relevant declarations are in
>> i915_gem_object_frontbuffer.h too.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Jouni Högander <jouni.hogander@intel.com>
Thanks for the reviews, pushed to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-03-11 10:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 18:17 [PATCH 0/7] drm/{i915, xe}/frontbuffer: refactor, move calls to parent interface Jani Nikula
2026-03-02 18:17 ` [PATCH 1/7] drm/i915/gem: relocate __i915_gem_object_{flush, invalidate}_frontbuffer() Jani Nikula
2026-03-04 14:20 ` Hogander, Jouni
2026-03-11 10:12 ` Jani Nikula [this message]
2026-03-02 18:17 ` [PATCH 2/7] drm/i915/gem: unify i915 gem object frontbuffer function names Jani Nikula
2026-03-05 6:41 ` Hogander, Jouni
2026-03-02 18:17 ` [PATCH 3/7] drm/i915/overlay: convert from struct intel_frontbuffer to i915_frontbuffer Jani Nikula
2026-03-05 7:07 ` Hogander, Jouni
2026-03-02 18:17 ` [PATCH 4/7] drm/intel: fix @dpt kernel-doc for parent interface Jani Nikula
2026-03-05 11:37 ` Hogander, Jouni
2026-03-02 18:17 ` [PATCH 5/7] drm/{i915, xe}/frontbuffer: move frontbuffer handling to " Jani Nikula
2026-03-06 6:54 ` Hogander, Jouni
2026-03-02 18:17 ` [PATCH 6/7] drm/i915/frontbuffer: call parent interface directly Jani Nikula
2026-03-06 7:05 ` Hogander, Jouni
2026-03-02 18:17 ` [PATCH 7/7] drm/i915/frontbuffer: reduce fb for frontbuffer abbreviation usage Jani Nikula
2026-03-06 7:25 ` Hogander, Jouni
2026-03-02 23:14 ` ✗ CI.checkpatch: warning for drm/{i915, xe}/frontbuffer: refactor, move calls to parent interface Patchwork
2026-03-02 23:16 ` ✓ CI.KUnit: success " Patchwork
2026-03-03 0:31 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-03 8:17 ` ✗ 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=f6e185b82149d2af71077605a47344f2114b6a27@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@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