From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933558AbcBZVmL (ORCPT ); Fri, 26 Feb 2016 16:42:11 -0500 Received: from mail.kernel.org ([198.145.29.136]:48250 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755244AbcBZVdr (ORCPT ); Fri, 26 Feb 2016 16:33:47 -0500 Message-Id: <20160226213340.790021589@goodmis.org> User-Agent: quilt/0.61-1 Date: Fri, 26 Feb 2016 16:32:40 -0500 From: Steven Rostedt To: linux-kernel@vger.kernel.org, linux-rt-users Cc: Thomas Gleixner , Carsten Emde , Sebastian Andrzej Siewior , John Kacur , Paul Gortmaker , , "Wolfgang M. Reimer" Subject: [PATCH RT 05/12] locking: locktorture: Do NOT include rwlock.h directly References: <20160226213235.253312067@goodmis.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Disposition: inline; filename=0005-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.18.27-rt26-rc1 stable review patch. If anyone has any objections, please let me know. ------------------ From: "Wolfgang M. Reimer" 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 Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Steven Rostedt --- kernel/locking/locktorture.c | 1 - 1 file changed, 1 deletion(-) diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c index ec8cce259779..aa60d919e336 100644 --- a/kernel/locking/locktorture.c +++ b/kernel/locking/locktorture.c @@ -24,7 +24,6 @@ #include #include #include -#include #include #include #include -- 2.7.0