diff options
Diffstat (limited to '')
| -rw-r--r-- | debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch b/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch new file mode 100644 index 000000000..2777ffd6a --- /dev/null +++ b/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch @@ -0,0 +1,34 @@ +From 651a6a4d30c878862e8ba912da5d7140d5e23a6e Mon Sep 17 00:00:00 2001 +From: "Wolfgang M. Reimer" <linuxball@gmail.com> +Date: Tue, 21 Jul 2015 16:20:07 +0200 +Subject: [PATCH 134/347] locking: locktorture: Do NOT include rwlock.h + directly +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.246-rt110.tar.xz + +Including rwlock.h directly will cause kernel builds to fail +if CONFIG_PREEMPT_RT_FULL is defined. The correct header file +(rwlock_rt.h OR rwlock.h) will be included by spinlock.h which +is included by locktorture.c anyway. + +Cc: stable-rt@vger.kernel.org +Signed-off-by: Wolfgang M. Reimer <linuxball@gmail.com> +Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> +--- + kernel/locking/locktorture.c | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c +index 95395ef5922a..5748c1936edb 100644 +--- a/kernel/locking/locktorture.c ++++ b/kernel/locking/locktorture.c +@@ -29,7 +29,6 @@ + #include <linux/kthread.h> + #include <linux/sched/rt.h> + #include <linux/spinlock.h> +-#include <linux/rwlock.h> + #include <linux/mutex.h> + #include <linux/rwsem.h> + #include <linux/smp.h> +-- +2.36.1 + |