From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/xe: Remove used xe_sync_entry_wait
Date: Wed, 17 Jul 2024 16:41:10 +0200 [thread overview]
Message-ID: <dee6ac05-b16e-4db2-bd63-bbe65323d64d@linux.intel.com> (raw)
In-Reply-To: <20240717140429.1396820-2-matthew.brost@intel.com>
On 7/17/2024 4:04 PM, Matthew Brost wrote:
> xe_sync_entry_wait is no longer used, remove it.
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> drivers/gpu/drm/xe/xe_sync.c | 8 --------
> drivers/gpu/drm/xe/xe_sync.h | 1 -
> 2 files changed, 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_sync.c b/drivers/gpu/drm/xe/xe_sync.c
> index f2e5e3c8c0cd..533246f42256 100644
> --- a/drivers/gpu/drm/xe/xe_sync.c
> +++ b/drivers/gpu/drm/xe/xe_sync.c
> @@ -204,14 +204,6 @@ int xe_sync_entry_parse(struct xe_device *xe, struct xe_file *xef,
> return 0;
> }
>
> -int xe_sync_entry_wait(struct xe_sync_entry *sync)
> -{
> - if (sync->fence)
> - dma_fence_wait(sync->fence, true);
> -
> - return 0;
> -}
> -
> int xe_sync_entry_add_deps(struct xe_sync_entry *sync, struct xe_sched_job *job)
> {
> int err;
> diff --git a/drivers/gpu/drm/xe/xe_sync.h b/drivers/gpu/drm/xe/xe_sync.h
> index 006dbf780793..256ffc1e54dc 100644
> --- a/drivers/gpu/drm/xe/xe_sync.h
> +++ b/drivers/gpu/drm/xe/xe_sync.h
> @@ -22,7 +22,6 @@ int xe_sync_entry_parse(struct xe_device *xe, struct xe_file *xef,
> struct xe_sync_entry *sync,
> struct drm_xe_sync __user *sync_user,
> unsigned int flags);
> -int xe_sync_entry_wait(struct xe_sync_entry *sync);
> int xe_sync_entry_add_deps(struct xe_sync_entry *sync,
> struct xe_sched_job *job);
> void xe_sync_entry_signal(struct xe_sync_entry *sync,
next prev parent reply other threads:[~2024-07-17 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 14:04 [PATCH 1/2] drm/xe: Validate user fence during creation Matthew Brost
2024-07-17 14:04 ` [PATCH 2/2] drm/xe: Remove used xe_sync_entry_wait Matthew Brost
2024-07-17 14:41 ` Nirmoy Das [this message]
2024-07-17 18:35 ` Dixit, Ashutosh
2024-07-17 19:06 ` Matthew Brost
2024-07-17 14:19 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Validate user fence during creation Patchwork
2024-07-17 14:19 ` ✓ CI.checkpatch: " Patchwork
2024-07-17 14:21 ` ✓ CI.KUnit: " Patchwork
2024-07-17 14:33 ` ✓ CI.Build: " Patchwork
2024-07-17 14:35 ` ✓ CI.Hooks: " Patchwork
2024-07-17 14:36 ` ✓ CI.checksparse: " Patchwork
2024-07-17 14:40 ` [PATCH 1/2] " Nirmoy Das
2024-07-17 15:12 ` ✓ CI.BAT: success for series starting with [1/2] " Patchwork
2024-07-17 19:55 ` ✗ 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=dee6ac05-b16e-4db2-bd63-bbe65323d64d@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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.