Re: [PATCH 1/1] 3.18.17-rt14 locktorture: Do NOT include rwlock.h directly

[linuxball <linuxball@gmail.com>]

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.

Signed-off-by: Wolfgang M. Reimer <linuxball@gmail.com>
---
  kernel/locking/locktorture.c | 1 -
  1 file changed, 1 deletion(-)

diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c
index ec8cce2..aa60d91 100644
--- a/kernel/locking/locktorture.c
+++ b/kernel/locking/locktorture.c
@@ -24,7 +24,6 @@
  #include <linux/module.h>
  #include <linux/kthread.h>
  #include <linux/spinlock.h>
-#include <linux/rwlock.h>
  #include <linux/mutex.h>
  #include <linux/rwsem.h>
  #include <linux/smp.h>
-- 
1.9.1

On 20.07.2015 17:47, Sebastian Andrzej Siewior wrote:
> * linuxball | 2015-07-20 11:33:12 [+0200]:
>
>> 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.
> Documentation/SubmittingPatches:
>      11) Sign your work
>
> Sebastian