Hi Andrzej, On Tue, Dec 13, 2022 at 01:19:50PM +0100, Andrzej Hajda wrote: > There is no need to use _i915_vma_move_to_active. > No functional changes. > > Signed-off-by: Andrzej Hajda <andrzej.ha...@intel.com>
both patches pushed in drm-intel-gt-next. Thanks, Andi > --- > drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.h > b/drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.h > index 1379fbc1443126..71a3ca8a886506 100644 > --- a/drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.h > +++ b/drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.h > @@ -38,7 +38,7 @@ igt_vma_move_to_active_unlocked(struct i915_vma *vma, > struct i915_request *rq, > int err; > > i915_vma_lock(vma); > - err = _i915_vma_move_to_active(vma, rq, &rq->fence, flags); > + err = i915_vma_move_to_active(vma, rq, flags); > i915_vma_unlock(vma); > return err; > } > -- > 2.34.1
