Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: chris@chris-wilson.co.uk
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Remove unwanted pointer unpacking
Date: Tue, 27 Sep 2022 08:34:30 +0100	[thread overview]
Message-ID: <a75c355d-24c7-41e1-4924-2689fde5c4e0@linux.intel.com> (raw)
In-Reply-To: <20220927054016.21474-1-niranjana.vishwanathapura@intel.com>


On 27/09/2022 06:40, Niranjana Vishwanathapura wrote:
> In await_fence_array(), unpacking syncobj pointer is not needed.
> Remove it.
> 
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
>   drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 5 -----
>   1 file changed, 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> index cd75b0ca2555..8f5796cf9c9c 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> @@ -2954,11 +2954,6 @@ await_fence_array(struct i915_execbuffer *eb,
>   	int err;
>   
>   	for (n = 0; n < eb->num_fences; n++) {
> -		struct drm_syncobj *syncobj;
> -		unsigned int flags;
> -
> -		syncobj = ptr_unpack_bits(eb->fences[n].syncobj, &flags, 2);
> -

Seems it was left hanging unused since 13149e8bafc4 ("drm/i915: add 
syncobj timeline support").

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

Tvrtko

>   		if (!eb->fences[n].dma_fence)
>   			continue;
>   

  parent reply	other threads:[~2022-09-27  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  5:40 [Intel-gfx] [PATCH] drm/i915: Remove unwanted pointer unpacking Niranjana Vishwanathapura
2022-09-27  6:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-09-27  6:52 ` [Intel-gfx] [PATCH] " Jani Nikula
2022-09-27 18:20   ` Niranjana Vishwanathapura
2022-09-27  7:34 ` Tvrtko Ursulin [this message]
2022-09-27 16:41 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2022-09-27 18:13 [Intel-gfx] [PATCH] " Niranjana Vishwanathapura

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=a75c355d-24c7-41e1-4924-2689fde5c4e0@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=niranjana.vishwanathapura@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