All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Lin, Shuicheng" <shuicheng.lin@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>,
	"Dugast, Francois" <francois.dugast@intel.com>,
	"Bai, Zongyao" <zongyao.bai@intel.com>
Subject: Re: [PATCH v2] drm/xe/uapi: Correct sync type definition in comments
Date: Wed, 25 Jun 2025 10:17:11 -0400	[thread overview]
Message-ID: <aFwE5xzuG9TATRtB@intel.com> (raw)
In-Reply-To: <DM4PR11MB54561CC1D8F1FC82EE89E8AAEA7BA@DM4PR11MB5456.namprd11.prod.outlook.com>

On Wed, Jun 25, 2025 at 05:38:06AM +0000, Lin, Shuicheng wrote:
> Hi maintainers:
> Could you please help me review and merge it?

pushed to drm-xe-next, thanks for the patch

> Thanks.
> 
> Shuicheng
> 
> On Mon, Jun 9, 2025 7:02 AM Shuicheng Lin wrote: 
> > Commit 37d078e51b4c ("drm/xe/uapi: Split xe_sync types from flags") renamed
> > some DRM_XE_SYNC_* defines but later commits kept using the old names.
> > Correct them with the new definition.
> > 
> > v2: correct fixes tag and update commit message to explain why (Lucas)
> > 
> > Fixes: 9329f0667215 ("drm/xe/uapi: Use LR abbrev for long-running vms")
> > Fixes: 4b437893a826 ("drm/xe/uapi: More uAPI documentation additions and
> > cosmetic updates")
> > Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Francois Dugast <francois.dugast@intel.com>
> > Cc: Zongyao Bai <zongyao.bai@intel.com>
> > Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
> > ---
> >  include/uapi/drm/xe_drm.h | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h index
> > 6a702ba7817c..5f1524f466a7 100644
> > --- a/include/uapi/drm/xe_drm.h
> > +++ b/include/uapi/drm/xe_drm.h
> > @@ -925,9 +925,9 @@ struct drm_xe_gem_mmap_offset {
> >   *  - %DRM_XE_VM_CREATE_FLAG_LR_MODE - An LR, or Long Running VM
> > accepts
> >   *    exec submissions to its exec_queues that don't have an upper time
> >   *    limit on the job execution time. But exec submissions to these
> > - *    don't allow any of the flags DRM_XE_SYNC_FLAG_SYNCOBJ,
> > - *    DRM_XE_SYNC_FLAG_TIMELINE_SYNCOBJ,
> > DRM_XE_SYNC_FLAG_DMA_BUF,
> > - *    used as out-syncobjs, that is, together with DRM_XE_SYNC_FLAG_SIGNAL.
> > + *    don't allow any of the sync types DRM_XE_SYNC_TYPE_SYNCOBJ,
> > + *    DRM_XE_SYNC_TYPE_TIMELINE_SYNCOBJ, used as out-syncobjs, that is,
> > + *    together with sync flag DRM_XE_SYNC_FLAG_SIGNAL.
> >   *    LR VMs can be created in recoverable page-fault mode using
> >   *    DRM_XE_VM_CREATE_FLAG_FAULT_MODE, if the device supports it.
> >   *    If that flag is omitted, the UMD can not rely on the slightly
> > @@ -1394,7 +1394,7 @@ struct drm_xe_sync {
> > 
> >  	/**
> >  	 * @timeline_value: Input for the timeline sync object. Needs to be
> > -	 * different than 0 when used
> > with %DRM_XE_SYNC_FLAG_TIMELINE_SYNCOBJ.
> > +	 * different than 0 when used
> > with %DRM_XE_SYNC_TYPE_TIMELINE_SYNCOBJ.
> >  	 */
> >  	__u64 timeline_value;
> > 
> > --
> > 2.25.1
> 

  reply	other threads:[~2025-06-25 14:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07  2:34 [PATCH] drm/xe/uapi: Correct sync type definition in comments Shuicheng Lin
2025-06-07  2:40 ` ✓ CI.Patch_applied: success for " Patchwork
2025-06-07  2:40 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-07  2:42 ` ✓ CI.KUnit: success " Patchwork
2025-06-07  2:52 ` ✓ CI.Build: " Patchwork
2025-06-07  2:55 ` ✓ CI.Hooks: " Patchwork
2025-06-07  2:56 ` ✓ CI.checksparse: " Patchwork
2025-06-07  3:41 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-07  5:10 ` [PATCH] " Lucas De Marchi
2025-06-08 23:06   ` Lin, Shuicheng
2025-06-08 23:01 ` [PATCH v2] " Shuicheng Lin
2025-06-25  5:38   ` Lin, Shuicheng
2025-06-25 14:17     ` Rodrigo Vivi [this message]
2025-06-08 23:07 ` ✓ CI.Patch_applied: success for drm/xe/uapi: Correct sync type definition in comments (rev2) Patchwork
2025-06-08 23:07 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-08 23:09 ` ✓ CI.KUnit: success " Patchwork
2025-06-08 23:19 ` ✓ CI.Build: " Patchwork
2025-06-08 23:22 ` ✓ CI.Hooks: " Patchwork
2025-06-08 23:23 ` ✓ CI.checksparse: " Patchwork
2025-06-09  0:24 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-09  6:55 ` ✓ Xe.CI.Full: success for drm/xe/uapi: Correct sync type definition in comments Patchwork
2025-06-09  8:41 ` ✗ Xe.CI.Full: failure for drm/xe/uapi: Correct sync type definition in comments (rev2) 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=aFwE5xzuG9TATRtB@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=shuicheng.lin@intel.com \
    --cc=zongyao.bai@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.