summaryrefslogtreecommitdiffstats
path: root/debian/patches-rt/0263-drm-i915-Don-t-disable-interrupts-independently-of-t.patch
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-05-08 04:15:14 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-05-08 04:15:14 +0000
commite549f10391e1fc78dab80e9b9ef524d214d4af40 (patch)
tree5358015c2d151febc170684ed8ddf2011b3ac4af /debian/patches-rt/0263-drm-i915-Don-t-disable-interrupts-independently-of-t.patch
parentMerging upstream version 4.19.282. (diff)
downloadlinux-e549f10391e1fc78dab80e9b9ef524d214d4af40.tar.xz
linux-e549f10391e1fc78dab80e9b9ef524d214d4af40.zip
Adding debian version 4.19.282-1.debian/4.19.282-1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'debian/patches-rt/0263-drm-i915-Don-t-disable-interrupts-independently-of-t.patch')
-rw-r--r--debian/patches-rt/0263-drm-i915-Don-t-disable-interrupts-independently-of-t.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/debian/patches-rt/0263-drm-i915-Don-t-disable-interrupts-independently-of-t.patch b/debian/patches-rt/0263-drm-i915-Don-t-disable-interrupts-independently-of-t.patch
index c6202c76b..3e70d62c2 100644
--- a/debian/patches-rt/0263-drm-i915-Don-t-disable-interrupts-independently-of-t.patch
+++ b/debian/patches-rt/0263-drm-i915-Don-t-disable-interrupts-independently-of-t.patch
@@ -1,8 +1,8 @@
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: Wed, 10 Apr 2019 11:01:37 +0200
-Subject: [PATCH 263/351] drm/i915: Don't disable interrupts independently of
+Subject: [PATCH 263/353] drm/i915: Don't disable interrupts independently of
the lock
-Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=797d3c7e24d525fcadd72c6f71220656625c88ef
+Origin: https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/commit?id=955d865790f6580d202d6a81658dc0a7b577ac78
The locks (timeline->lock and rq->lock) need to be taken with disabled
interrupts. This is done in __retire_engine_request() by disabling the