Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: [Intel-xe] [PATCH 1/7] drm/xe: Add empty def for i915_gem_object_flush_if_display
Date: Fri, 15 Sep 2023 10:48:12 +0300	[thread overview]
Message-ID: <20230915074818.903353-2-jouni.hogander@intel.com> (raw)
In-Reply-To: <20230915074818.903353-1-jouni.hogander@intel.com>

We don't need i915_gem_object_flush_if_display on Xe side. Add empty
define to tackle compilation errors with display code where it's used.

Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
---
 drivers/gpu/drm/xe/xe_bo.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/xe/xe_bo.h b/drivers/gpu/drm/xe/xe_bo.h
index 4a68d869b3b5..b2c139586d97 100644
--- a/drivers/gpu/drm/xe/xe_bo.h
+++ b/drivers/gpu/drm/xe/xe_bo.h
@@ -307,6 +307,7 @@ static inline unsigned int xe_sg_segment_size(struct device *dev)
 
 #define i915_gem_object_get_frontbuffer(obj)		NULL
 #define i915_gem_object_set_frontbuffer(obj, front)	(front)
+#define i915_gem_object_flush_if_display(obj)		((void)(obj))
 
 #if IS_ENABLED(CONFIG_DRM_XE_KUNIT_TEST)
 /**
-- 
2.34.1


  reply	other threads:[~2023-09-15  7:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  7:48 [Intel-xe] [PATCH 0/7] Frontbuffer tracking and dirtyfb Jouni Högander
2023-09-15  7:48 ` Jouni Högander [this message]
2023-09-15  7:48 ` [Intel-xe] [PATCH 2/7] fixup! FIXME: drm/i915/display: Remaining changes to make xe compile Jouni Högander
2023-09-15  7:48 ` [Intel-xe] [PATCH 3/7] drm/i915/fbc: Clear frontbuffer busy bits on flip Jouni Högander
2023-09-15  7:48 ` [Intel-xe] [PATCH 4/7] drm/i915/psr: " Jouni Högander
2023-09-15  7:48 ` [Intel-xe] [PATCH 5/7] drm/i915: Add new frontbuffer tracking interface to queue flush Jouni Högander
2023-09-15  7:48 ` [Intel-xe] [PATCH 6/7] drm/i915: Handle dma fences in dirtyfb callback Jouni Högander
2023-09-15  7:48 ` [Intel-xe] [PATCH 7/7] drm/i915/display: Use intel_bo_to_drm_bo instead of obj->base Jouni Högander
2023-09-15  7:56 ` [Intel-xe] ✓ CI.Patch_applied: success for Frontbuffer tracking and dirtyfb Patchwork
2023-09-15  7:56 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-15  7:57 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-15  8:04 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-15  8:05 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-15  8:06 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-15  8:38 ` [Intel-xe] ✓ CI.BAT: success " 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=20230915074818.903353-2-jouni.hogander@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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