Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Upadhyay, Tejas" <tejas.upadhyay@intel.com>
Cc: "Wang, X" <x.wang@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: remove redundant check in xe_vm_create_ioctl()
Date: Mon, 10 Mar 2025 13:33:21 -0400	[thread overview]
Message-ID: <Z88iYX5u38A-hl8p@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6204E2A69594960A4A7AA43981C92@SJ1PR11MB6204.namprd11.prod.outlook.com>

On Mon, Mar 03, 2025 at 06:03:00AM +0000, Upadhyay, Tejas wrote:
> 
> 
> > -----Original Message-----
> > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Xin
> > Wang
> > Sent: Monday, March 3, 2025 6:20 AM
> > To: intel-xe@lists.freedesktop.org
> > Cc: Wang, X <x.wang@intel.com>; Vivi, Rodrigo <rodrigo.vivi@intel.com>
> > Subject: [PATCH] drm/xe: remove redundant check in xe_vm_create_ioctl()
> > 
> > The check for args->extensions is repeated twice in xe_vm_create_ioctl().
> > This commit removes the redundant check to streamline the code.
> 
> Fixes tag?

Fixes: 7224788f6756 ("drm/xe: Kill XE_VM_PROPERTY_BIND_OP_ERROR_CAPTURE_ADDRESS extension")

My Bad... sorry.

pushed with the tag to drm-xe-next

Thanks for the patch and review

> 
> > 
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Signed-off-by: Xin Wang <x.wang@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_vm.c | 3 ---
> >  1 file changed, 3 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c index
> > 996000f2424e..eb76f6854b2f 100644
> > --- a/drivers/gpu/drm/xe/xe_vm.c
> > +++ b/drivers/gpu/drm/xe/xe_vm.c
> > @@ -1798,9 +1798,6 @@ int xe_vm_create_ioctl(struct drm_device *dev,
> > void *data,
> >  			 args->flags &
> > DRM_XE_VM_CREATE_FLAG_FAULT_MODE))
> >  		return -EINVAL;
> > 
> > -	if (XE_IOCTL_DBG(xe, args->extensions))
> > -		return -EINVAL;
> > -
> 
> LGTM,
> Reviewed-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
> 
> >  	if (args->flags & DRM_XE_VM_CREATE_FLAG_SCRATCH_PAGE)
> >  		flags |= XE_VM_FLAG_SCRATCH_PAGE;
> >  	if (args->flags & DRM_XE_VM_CREATE_FLAG_LR_MODE)
> > --
> > 2.43.0
> 

      reply	other threads:[~2025-03-10 17:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03  0:49 [PATCH] drm/xe: remove redundant check in xe_vm_create_ioctl() Xin Wang
2025-03-03  0:54 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-03  0:54 ` ✓ CI.checkpatch: " Patchwork
2025-03-03  0:55 ` ✓ CI.KUnit: " Patchwork
2025-03-03  1:12 ` ✓ CI.Build: " Patchwork
2025-03-03  1:14 ` ✓ CI.Hooks: " Patchwork
2025-03-03  1:17 ` ✓ CI.checksparse: " Patchwork
2025-03-03  1:36 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-03  2:29 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-03  6:03 ` [PATCH] " Upadhyay, Tejas
2025-03-10 17:33   ` Rodrigo Vivi [this message]

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=Z88iYX5u38A-hl8p@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=tejas.upadhyay@intel.com \
    --cc=x.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox