From: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
To: Saswat Jung Khadka <saswatjungkhadka@gmail.com>, zack.rusin@broadcom.com
Cc: bcm-kernel-feedback-list@broadcom.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/vmwgfx: Remove unused vmw_goal_waiter_add/remove
Date: Fri, 24 Jul 2026 13:12:19 -0700 [thread overview]
Message-ID: <68f99546-7ca4-4aa2-ba5c-aa36204c2f8a@broadcom.com> (raw)
In-Reply-To: <20260723043605.2195-1-saswatjungkhadka@gmail.com>
On 7/22/26 9:36 PM, Saswat Jung Khadka wrote:
> vmw_goal_waiter_add() and vmw_goal_waiter_remove() have had no
> callers since commit db6a94b26354 ("drm/vmwgfx: Implement
> dma_fence_ops properly"), which removed their only call site.
> Their sibling functions vmw_seqno_waiter_add/remove are still
> in active use, confirming these are leftover dead code.
>
> Signed-off-by: Saswat Jung Khadka <saswatjungkhadka@gmail.com>
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 2 --
> drivers/gpu/drm/vmwgfx/vmwgfx_irq.c | 12 ------------
> 2 files changed, 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
> index 38bea8aba..d84e077ed 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
> @@ -1026,8 +1026,6 @@ extern int vmw_fallback_wait(struct vmw_private *dev_priv,
> unsigned long timeout);
> bool vmw_seqno_waiter_add(struct vmw_private *dev_priv);
> bool vmw_seqno_waiter_remove(struct vmw_private *dev_priv);
> -bool vmw_goal_waiter_add(struct vmw_private *dev_priv);
> -bool vmw_goal_waiter_remove(struct vmw_private *dev_priv);
> bool vmw_generic_waiter_add(struct vmw_private *dev_priv, u32 flag,
> int *waiter_count);
> bool vmw_generic_waiter_remove(struct vmw_private *dev_priv,
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_irq.c b/drivers/gpu/drm/vmwgfx/vmwgfx_irq.c
> index 05773eb39..88c77226c 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_irq.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_irq.c
> @@ -273,18 +273,6 @@ bool vmw_seqno_waiter_remove(struct vmw_private *dev_priv)
> &dev_priv->fence_queue_waiters);
> }
>
> -bool vmw_goal_waiter_add(struct vmw_private *dev_priv)
> -{
> - return vmw_generic_waiter_add(dev_priv, vmw_irqflag_fence_goal(dev_priv),
> - &dev_priv->goal_queue_waiters);
> -}
> -
> -bool vmw_goal_waiter_remove(struct vmw_private *dev_priv)
> -{
> - return vmw_generic_waiter_remove(dev_priv, vmw_irqflag_fence_goal(dev_priv),
> - &dev_priv->goal_queue_waiters);
> -}
> -
> static void vmw_irq_preinstall(struct drm_device *dev)
> {
> struct vmw_private *dev_priv = vmw_priv(dev);
LGTM!
Reviewed-by: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
--
Maaz Mombasawala <maaz.mombasawala@broadcom.com>
prev parent reply other threads:[~2026-07-24 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 8:00 [PATCH] " Saswat PC Ubuntu
2026-07-23 4:36 ` [PATCH v2] " Saswat Jung Khadka
2026-07-24 20:12 ` Maaz Mombasawala [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=68f99546-7ca4-4aa2-ba5c-aa36204c2f8a@broadcom.com \
--to=maaz.mombasawala@broadcom.com \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=saswatjungkhadka@gmail.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=zack.rusin@broadcom.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
all inboxes | Powered by JetHome®