From: "John Kacur" <jkacur@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ingo Molnar" <mingo@elte.hu>
Subject: [PATCH] Compile problems in locking-selftest.c with CONFIG_DEBUG_PREEMPT
Date: Fri, 15 Aug 2008 17:57:32 +0200 [thread overview]
Message-ID: <520f0cf10808150857u5803d86cj205e671f640c81c4@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
The attached patch fixes the following compiler error in the rt-kernel
if CONFIG_DEBUG_PREEMPT is enabled.
lib/locking-selftest.c: In function 'dotest':
lib/locking-selftest.c:951: error: incompatible types in initialization
lib/locking-selftest.c:1003: error: incompatible types in assignment
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: locking-selftest-fix.patch --]
[-- Type: text/x-patch; name=locking-selftest-fix.patch, Size: 907 bytes --]
Subject: Compile problems in locking-selftest.c with CONFIG_DEBUG_PREEMPT
lib/locking-selftest.c: In function ‘dotest’:
lib/locking-selftest.c:951: error: incompatible types in initialization
lib/locking-selftest.c:1003: error: incompatible types in assignment
Signed-off-by: John Kacur <jkacur at gmail dot com>
Index: linux-2.6.26.1-rt1.jk/lib/locking-selftest.c
===================================================================
--- linux-2.6.26.1-rt1.jk.orig/lib/locking-selftest.c
+++ linux-2.6.26.1-rt1.jk/lib/locking-selftest.c
@@ -948,7 +948,7 @@ static void dotest(void (*testcase_fn)(v
unsigned long saved_preempt_count = preempt_count();
int expected_failure = 0;
#if defined(CONFIG_DEBUG_PREEMPT) && defined(CONFIG_DEBUG_RT_MUTEXES)
- int saved_lock_count = current->lock_count;
+ atomic_t saved_lock_count = current->lock_count;
#endif
WARN_ON(irqs_disabled());
reply other threads:[~2008-08-15 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=520f0cf10808150857u5803d86cj205e671f640c81c4@mail.gmail.com \
--to=jkacur@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).