From: Jani Nikula <jani.nikula@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH 0/8] Backport i915_sw_fence to dma fence conversion
Date: Tue, 07 Nov 2023 14:56:37 +0200 [thread overview]
Message-ID: <87v8adyb5m.fsf@intel.com> (raw)
In-Reply-To: <20231106064834.161647-1-jouni.hogander@intel.com>
On Mon, 06 Nov 2023, Jouni Högander <jouni.hogander@intel.com> wrote:
> In drm-intel-next branch we have now removed usage of i915_sw_fence
> from display code and using dma_fence instead. Backport these patches
> and revert related FIXME patches and other branch internal changes
> from drm-xe-intel branch.
>
> For now handle i915_gem_fence_wait_priority by adding empty defines
> into compatibility headers. This is not interfering ongoing work to
> remove i915_gem_fence_wait_priority from i915. These empty defines can
> be easily removed when that work is done.
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Other than the comment on patch 1, the series is
Acked-by: Jani Nikula <jani.nikula@intel.com>
>
> Jouni Högander (8):
> fixup! drm/xe/display: Implement display support
> Revert "FIXME: drm/i915: fence stuff"
> Revert "drm/xe/display: Append dma_buf fences to framebuffer fences"
> fixup! drm/xe/display: Implement display support
> drm/i915/display: Use dma_fence interfaces instead of i915_sw_fence
> drm/i915/display: Use intel_bo_to_drm_bo instead of obj->base
> fixup! drm/xe/display: Implement display support
> fixup! FIXME: drm/i915/display: Remaining changes to make xe compile
>
> drivers/gpu/drm/i915/display/intel_atomic.c | 5 -
> .../gpu/drm/i915/display/intel_atomic_plane.c | 101 ++++++++----------
> drivers/gpu/drm/i915/display/intel_display.c | 91 +++-------------
> .../drm/i915/display/intel_display_types.h | 4 -
> .../drm/xe/compat-i915-headers/i915_config.h | 8 +-
> .../gpu/drm/xe/compat-i915-headers/i915_drv.h | 7 +-
> 6 files changed, 69 insertions(+), 147 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-11-07 12:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 6:48 [Intel-xe] [PATCH 0/8] Backport i915_sw_fence to dma fence conversion Jouni Högander
2023-11-06 6:48 ` [Intel-xe] [PATCH 1/8] fixup! drm/xe/display: Implement display support Jouni Högander
2023-11-07 12:54 ` Jani Nikula
2023-11-07 13:19 ` Hogander, Jouni
2023-11-07 13:41 ` Jani Nikula
2023-11-06 6:48 ` [Intel-xe] [PATCH 2/8] Revert "FIXME: drm/i915: fence stuff" Jouni Högander
2023-11-06 6:48 ` [Intel-xe] [PATCH 3/8] Revert "drm/xe/display: Append dma_buf fences to framebuffer fences" Jouni Högander
2023-11-06 6:48 ` [Intel-xe] [PATCH 4/8] fixup! drm/xe/display: Implement display support Jouni Högander
2023-11-06 6:48 ` [Intel-xe] [PATCH 5/8] drm/i915/display: Use dma_fence interfaces instead of i915_sw_fence Jouni Högander
2023-11-06 6:48 ` [Intel-xe] [PATCH 6/8] drm/i915/display: Use intel_bo_to_drm_bo instead of obj->base Jouni Högander
2023-11-06 6:48 ` [Intel-xe] [PATCH 7/8] fixup! drm/xe/display: Implement display support Jouni Högander
2023-11-06 6:48 ` [Intel-xe] [PATCH 8/8] fixup! FIXME: drm/i915/display: Remaining changes to make xe compile Jouni Högander
2023-11-06 6:51 ` [Intel-xe] ✓ CI.Patch_applied: success for Backport i915_sw_fence to dma fence conversion Patchwork
2023-11-06 6:51 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-11-06 6:53 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-11-06 7:00 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-06 7:03 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-06 7:04 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-11-06 7:33 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-11-07 12:56 ` Jani Nikula [this message]
2023-11-08 6:06 ` [Intel-xe] [PATCH 0/8] " Hogander, Jouni
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=87v8adyb5m.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@intel.com \
--cc=rodrigo.vivi@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.