All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH] drm/xe/display: drop duplicate display->fb_tracking.lock init
Date: Fri, 16 May 2025 12:55:14 +0300	[thread overview]
Message-ID: <20250516095514.398320-1-jani.nikula@intel.com> (raw)

The spinlock is initialized in intel_display_driver_early_probe(). Drop
the extra init.

Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
 drivers/gpu/drm/xe/display/xe_display.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
index 699f401eff10..1fcca7acaef4 100644
--- a/drivers/gpu/drm/xe/display/xe_display.c
+++ b/drivers/gpu/drm/xe/display/xe_display.c
@@ -109,8 +109,6 @@ int xe_display_create(struct xe_device *xe)
 
 	xe->display = &xe->__display;
 
-	spin_lock_init(&display->fb_tracking.lock);
-
 	display->hotplug.dp_wq = alloc_ordered_workqueue("xe-dp", 0);
 
 	return drmm_add_action_or_reset(&xe->drm, display_destroy, NULL);
-- 
2.39.5


             reply	other threads:[~2025-05-16  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16  9:55 Jani Nikula [this message]
2025-05-16  9:59 ` [PATCH] drm/xe/display: drop duplicate display->fb_tracking.lock init Matthew Auld
2025-05-16 12:19   ` Jani Nikula
2025-05-16 10:13 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-16 10:13 ` ✓ CI.checkpatch: " Patchwork
2025-05-16 10:14 ` ✓ CI.KUnit: " Patchwork
2025-05-16 10:24 ` ✓ CI.Build: " Patchwork
2025-05-16 10:27 ` ✓ CI.Hooks: " Patchwork
2025-05-16 10:28 ` ✓ CI.checksparse: " Patchwork
2025-05-16 10:50 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-17  3:07 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-27  2:58 ` ✗ CI.Patch_applied: " Patchwork

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=20250516095514.398320-1-jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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.