From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v3 3/4] drm/i915/display: Remove i915_gem_object_types.h from intel_frontbuffer.h
Date: Wed, 7 Jun 2023 11:12:26 +0300 [thread overview]
Message-ID: <20230607081227.96992-4-jouni.hogander@intel.com> (raw)
In-Reply-To: <20230607081227.96992-1-jouni.hogander@intel.com>
Now as we have removed all the references to internals of i915_gem_object
from the frontbuffer header we can also remove including
i915_gem_object_types.h.
Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
---
drivers/gpu/drm/i915/display/intel_frontbuffer.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_frontbuffer.h b/drivers/gpu/drm/i915/display/intel_frontbuffer.h
index eeccc847331d..72d89be3284b 100644
--- a/drivers/gpu/drm/i915/display/intel_frontbuffer.h
+++ b/drivers/gpu/drm/i915/display/intel_frontbuffer.h
@@ -28,7 +28,6 @@
#include <linux/bits.h>
#include <linux/kref.h>
-#include "gem/i915_gem_object_types.h"
#include "i915_active_types.h"
struct drm_i915_private;
--
2.34.1
next prev parent reply other threads:[~2023-06-07 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 8:12 [Intel-gfx] [PATCH v3 0/4] Do not access i915_gem_object members from frontbuffer tracking Jouni Högander
2023-06-07 8:12 ` [Intel-gfx] [PATCH v3 1/4] drm/i915: Add macros to get i915 device from i915_gem_object Jouni Högander
2023-06-07 8:12 ` [Intel-gfx] [PATCH v3 2/4] drm/i915: Add getter/setter for i915_gem_object->frontbuffer Jouni Högander
2023-06-07 8:12 ` Jouni Högander [this message]
2023-06-07 8:12 ` [Intel-gfx] [PATCH v3 4/4] drm/i915: Add function to clear scanout flag for vmas Jouni Högander
2023-06-07 9:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Do not access i915_gem_object members from frontbuffer tracking (rev3) Patchwork
2023-06-07 10:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-07 21:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230607081227.96992-4-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@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