From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/5] drm/i915: make struct intel_frontbuffer opaque
Date: Mon, 17 Jun 2024 17:18:57 +0300 [thread overview]
Message-ID: <cover.1718633874.git.jani.nikula@intel.com> (raw)
Hide the struct intel_frontbuffer implementation to add more clarity in
the interface boundaries.
Jani Nikula (5):
drm/i915/frontbuffer: un-inline frontbuffer bits checks
drm/i915/frontbuffer: hide ->bits more
drm/i915/frontbuffer: add low-level kref accessors
drm/i915/frontbuffer: hide ->write
drm/i915/frontbuffer: make struct intel_frontbuffer opaque
drivers/gpu/drm/i915/display/intel_fb.c | 2 +-
.../gpu/drm/i915/display/intel_frontbuffer.c | 57 +++++++++++++++++--
.../gpu/drm/i915/display/intel_frontbuffer.h | 53 ++++++-----------
.../drm/i915/display/intel_plane_initial.c | 2 +-
.../i915/gem/i915_gem_object_frontbuffer.h | 4 +-
drivers/gpu/drm/i915/i915_vma.c | 2 +-
drivers/gpu/drm/xe/display/xe_plane_initial.c | 2 +-
7 files changed, 75 insertions(+), 47 deletions(-)
--
2.39.2
next reply other threads:[~2024-06-17 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 14:18 Jani Nikula [this message]
2024-06-17 14:18 ` [PATCH 1/5] drm/i915/frontbuffer: un-inline frontbuffer bits checks Jani Nikula
2024-06-17 14:18 ` [PATCH 2/5] drm/i915/frontbuffer: hide ->bits more Jani Nikula
2024-06-17 14:19 ` [PATCH 3/5] drm/i915/frontbuffer: add low-level kref accessors Jani Nikula
2024-06-17 14:19 ` [PATCH 4/5] drm/i915/frontbuffer: hide ->write Jani Nikula
2024-06-17 14:19 ` [PATCH 5/5] drm/i915/frontbuffer: make struct intel_frontbuffer opaque Jani Nikula
2024-06-18 23:54 ` kernel test robot
2024-06-17 14:49 ` ✓ CI.Patch_applied: success for drm/i915: " Patchwork
2024-06-17 14:50 ` ✓ CI.checkpatch: " Patchwork
2024-06-17 14:51 ` ✓ CI.KUnit: " 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.1718633874.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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