From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Francois Dugast <francois.dugast@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe/uapi: Remove DRM_IOCTL_XE_EXEC_QUEUE_SET_PROPERTY
Date: Wed, 6 Dec 2023 11:26:18 -0500 [thread overview]
Message-ID: <ZXCgqvhDlMiEJNFo@intel.com> (raw)
In-Reply-To: <3v6lvfmd37hezn6tudgzrwv235f7wv4wct4d7zswa5qres7sfx@jovwzf4vgh2l>
On Wed, Dec 06, 2023 at 10:16:22AM -0600, Lucas De Marchi wrote:
> On Wed, Dec 06, 2023 at 04:06:17PM +0000, Francois Dugast wrote:
> > The exec_queue_set_property feature was removed in a previous
> > commit ("drm/xe/uapi: Kill exec_queue_set_property") and is no
> > longer usable, struct drm_xe_exec_queue_set_property does not
> > exist anymore, so let's remove this.
my bad, sorry
> >
> > Signed-off-by: Francois Dugast <francois.dugast@intel.com>
>
> should probably be a fixup to that patch? Anyway,
no because it is in the uapi header that gets "copied" by the UMDs
and IGT already merged and Mesa likely... and we cannot do fixup
on their sides.
Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> Lucas De Marchi
>
> > ---
> > 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 dee750385161..346007e8074d 100644
> > --- a/include/uapi/drm/xe_drm.h
> > +++ b/include/uapi/drm/xe_drm.h
> > @@ -53,7 +53,6 @@ extern "C" {
> > #define DRM_IOCTL_XE_VM_BIND DRM_IOW(DRM_COMMAND_BASE + DRM_XE_VM_BIND, struct drm_xe_vm_bind)
> > #define DRM_IOCTL_XE_EXEC_QUEUE_CREATE DRM_IOWR(DRM_COMMAND_BASE + DRM_XE_EXEC_QUEUE_CREATE, struct drm_xe_exec_queue_create)
> > #define DRM_IOCTL_XE_EXEC_QUEUE_DESTROY DRM_IOW(DRM_COMMAND_BASE + DRM_XE_EXEC_QUEUE_DESTROY, struct drm_xe_exec_queue_destroy)
> > -#define DRM_IOCTL_XE_EXEC_QUEUE_SET_PROPERTY DRM_IOW(DRM_COMMAND_BASE + DRM_XE_EXEC_QUEUE_SET_PROPERTY, struct drm_xe_exec_queue_set_property)
> > #define DRM_IOCTL_XE_EXEC_QUEUE_GET_PROPERTY DRM_IOWR(DRM_COMMAND_BASE + DRM_XE_EXEC_QUEUE_GET_PROPERTY, struct drm_xe_exec_queue_get_property)
> > #define DRM_IOCTL_XE_EXEC DRM_IOW(DRM_COMMAND_BASE + DRM_XE_EXEC, struct drm_xe_exec)
> > #define DRM_IOCTL_XE_WAIT_USER_FENCE DRM_IOWR(DRM_COMMAND_BASE + DRM_XE_WAIT_USER_FENCE, struct drm_xe_wait_user_fence)
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2023-12-06 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 16:06 [Intel-xe] [PATCH] drm/xe/uapi: Remove DRM_IOCTL_XE_EXEC_QUEUE_SET_PROPERTY Francois Dugast
2023-12-06 16:16 ` Lucas De Marchi
2023-12-06 16:26 ` Rodrigo Vivi [this message]
2023-12-06 16:33 ` Lucas De Marchi
2023-12-06 17:42 ` Rodrigo Vivi
2023-12-06 17:48 ` Lucas De Marchi
2023-12-06 17:52 ` Souza, Jose
2023-12-06 18:11 ` Rodrigo Vivi
2023-12-06 23:01 ` Lucas De Marchi
2023-12-06 17:06 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-12-06 17:06 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-12-06 17:07 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-12-06 17:15 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-12-06 17:15 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-12-06 17:16 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-12-06 17:52 ` [Intel-xe] ✓ CI.BAT: " 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=ZXCgqvhDlMiEJNFo@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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.