Re: [PATCH] locking: locktorture: Do not include rwlock.h directly

2019-09-18 Thread Paul E. McKenney
On Tue, Sep 17, 2019 at 11:24:04PM -0700, Davidlohr Bueso wrote: > On Tue, 17 Sep 2019, Paul E. McKenney wrote: > > > On Tue, Sep 17, 2019 at 12:16:14AM -0700, Davidlohr Bueso wrote: > > > On Mon, 16 Sep 2019, Sebastian Andrzej Siewior wrote: > > > > > > > From: Wolfgang M. Reimer > > > > > > >

Re: [PATCH] locking: locktorture: Do not include rwlock.h directly

2019-09-17 Thread Davidlohr Bueso
On Tue, 17 Sep 2019, Paul E. McKenney wrote: On Tue, Sep 17, 2019 at 12:16:14AM -0700, Davidlohr Bueso wrote: On Mon, 16 Sep 2019, Sebastian Andrzej Siewior wrote: > From: Wolfgang M. Reimer > > Including rwlock.h directly will cause kernel builds to fail > if CONFIG_PREEMPT_RT is defined. Th

Re: [PATCH] locking: locktorture: Do not include rwlock.h directly

2019-09-17 Thread Paul E. McKenney
On Tue, Sep 17, 2019 at 12:16:14AM -0700, Davidlohr Bueso wrote: > On Mon, 16 Sep 2019, Sebastian Andrzej Siewior wrote: > > > From: Wolfgang M. Reimer > > > > Including rwlock.h directly will cause kernel builds to fail > > if CONFIG_PREEMPT_RT is defined. The correct header file > > (rwlock_rt

Re: [PATCH] locking: locktorture: Do not include rwlock.h directly

2019-09-17 Thread Davidlohr Bueso
On Mon, 16 Sep 2019, Sebastian Andrzej Siewior wrote: From: Wolfgang M. Reimer Including rwlock.h directly will cause kernel builds to fail if CONFIG_PREEMPT_RT is defined. The correct header file (rwlock_rt.h OR rwlock.h) will be included by spinlock.h which is included by locktorture.c anywa

Re: [PATCH] locking: locktorture: Do not include rwlock.h directly

2019-09-16 Thread Paul E. McKenney
On Mon, Sep 16, 2019 at 04:54:04PM +0200, Sebastian Andrzej Siewior wrote: > From: Wolfgang M. Reimer > > Including rwlock.h directly will cause kernel builds to fail > if CONFIG_PREEMPT_RT is defined. The correct header file > (rwlock_rt.h OR rwlock.h) will be included by spinlock.h which > is i

[PATCH] locking: locktorture: Do not include rwlock.h directly

2019-09-16 Thread Sebastian Andrzej Siewior
From: Wolfgang M. Reimer Including rwlock.h directly will cause kernel builds to fail if CONFIG_PREEMPT_RT 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. Remove the include of linux/rwlock.h. Signed-off-by: