All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Remove dead code around intel_atomic_helper->free_list
Date: Tue, 14 Nov 2023 10:48:12 +0200	[thread overview]
Message-ID: <ZVM0TAMROaONQWEF@intel.com> (raw)
In-Reply-To: <20231110082455.3061913-1-jouni.hogander@intel.com>

On Fri, Nov 10, 2023 at 10:24:55AM +0200, Jouni Högander wrote:
> After switching to directly using dma_fence instead of i915_sw_fence we
> have left some dead code around intel_atomic_helper->free_list. Remove that
> dead code.
> 
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display.c  | 20 -------------------
>  .../gpu/drm/i915/display/intel_display_core.h |  6 ------
>  .../drm/i915/display/intel_display_driver.c   |  7 -------
>  3 files changed, 33 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index 3effafcbb411..387acf21b794 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -7086,24 +7086,6 @@ static void skl_commit_modeset_enables(struct intel_atomic_state *state)
>  	drm_WARN_ON(&dev_priv->drm, update_pipes);
>  }
>  
> -static void intel_atomic_helper_free_state(struct drm_i915_private *dev_priv)
> -{
> -	struct intel_atomic_state *state, *next;
> -	struct llist_node *freed;
> -
> -	freed = llist_del_all(&dev_priv->display.atomic_helper.free_list);
> -	llist_for_each_entry_safe(state, next, freed, freed)

state.freed is also dead.

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2023-11-14  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10  8:24 [Intel-gfx] [PATCH] drm/i915/display: Remove dead code around intel_atomic_helper->free_list Jouni Högander
2023-11-10 12:08 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-11-10 12:13 ` [Intel-gfx] [PATCH] " Jani Nikula
2023-11-10 12:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-11-10 18:16 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-13  8:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: Remove dead code around intel_atomic_helper->free_list (rev2) Patchwork
2023-11-13  8:52 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-13 17:36 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: Remove dead code around intel_atomic_helper->free_list (rev3) Patchwork
2023-11-13 17:55 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-14  8:48 ` Ville Syrjälä [this message]
2023-11-14 13:48   ` [Intel-gfx] [PATCH] drm/i915/display: Remove dead code around intel_atomic_helper->free_list Hogander, Jouni

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=ZVM0TAMROaONQWEF@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jouni.hogander@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.