All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe/uapi: Remove DRM_XE_VM_BIND_FLAG_ASYNC comment left over
Date: Tue, 26 Dec 2023 13:32:52 -0500	[thread overview]
Message-ID: <ZYscVGNS0Mlxn0ec@intel.com> (raw)
In-Reply-To: <20231226172321.61518-1-jose.souza@intel.com>

On Tue, Dec 26, 2023 at 09:23:21AM -0800, José Roberto de Souza wrote:
> This a comment left over of commit 52b226320b63
> ("drm/xe/uapi: Remove sync binds").

d3d767396a02 ("drm/xe/uapi: Remove sync binds")

> 
> Cc: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>

Fixes: d3d767396a02 ("drm/xe/uapi: Remove sync binds")

With the fixed reference above:

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  include/uapi/drm/xe_drm.h | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> index 9fa3ae324731a..50bbea0992d9c 100644
> --- a/include/uapi/drm/xe_drm.h
> +++ b/include/uapi/drm/xe_drm.h
> @@ -832,7 +832,6 @@ struct drm_xe_vm_destroy {
>   *
>   * and the @flags can be:
>   *  - %DRM_XE_VM_BIND_FLAG_READONLY
> - *  - %DRM_XE_VM_BIND_FLAG_ASYNC
>   *  - %DRM_XE_VM_BIND_FLAG_IMMEDIATE - Valid on a faulting VM only, do the
>   *    MAP operation immediately rather than deferring the MAP to the page
>   *    fault handler.
> -- 
> 2.43.0
> 

  reply	other threads:[~2023-12-26 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 17:23 [PATCH] drm/xe/uapi: Remove DRM_XE_VM_BIND_FLAG_ASYNC comment left over José Roberto de Souza
2023-12-26 18:32 ` Rodrigo Vivi [this message]
2024-01-04  9:32 ` ✗ CI.Patch_applied: failure for " 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=ZYscVGNS0Mlxn0ec@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jose.souza@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.