From: Jan Altenberg <tb10alj@tglx.de>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: [PATCH] realtime-preempt patch-2.6.15-rt19 compile error (was: realtime-preempt patch-2.6.15-rt18 issues)
Date: Tue, 07 Mar 2006 10:40:02 +0100 [thread overview]
Message-ID: <440D54F2.2080009@tglx.de> (raw)
In-Reply-To: <4547.195.245.190.94.1141657830.squirrel@www.rncbc.org>
Hi,
> -rt19 doesn't compile here (either with CONFIG_EMBEDDED=y or not):
same problem here. Looks like a typo...
Am I right?
Signed-off-by: Jan Altenberg <tb10alj@tglx.de>
--------------------------------------------------
--- slab.c.orig 2006-03-07 10:27:35.000000000 +0100
+++ slab.c 2006-03-07 10:28:17.000000000 +0100
@@ -700,7 +700,7 @@ static struct kmem_cache cache_cache = {
.shared = 1,
.buffer_size = sizeof(struct kmem_cache),
.flags = SLAB_NO_REAP,
- .spinlock = SPIN_LOCK_UNLOCKED(&cache_cache.spinlock),
+ .spinlock = SPIN_LOCK_UNLOCKED(cache_cache.spinlock),
.name = "kmem_cache",
#if DEBUG
.obj_size = sizeof(struct kmem_cache),
next prev parent reply other threads:[~2006-03-07 9:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 12:11 realtime-preempt patch-2.6.15-rt18 issues Rui Nuno Capela
2006-03-06 12:35 ` Ingo Molnar
2006-03-06 13:24 ` Ingo Molnar
2006-03-06 15:10 ` Rui Nuno Capela
2006-03-07 9:40 ` Jan Altenberg [this message]
2006-03-07 11:27 ` [PATCH] realtime-preempt patch-2.6.15-rt19 compile error (was: realtime-preempt patch-2.6.15-rt18 issues) Ingo Molnar
2006-03-07 12:33 ` Rui Nuno Capela
2006-03-10 7:44 ` realtime-preempt patch-2.6.15-rt18 issues Jan Altenberg
2006-03-14 23:13 ` [PATCH] realtime-preempt patch-2.6.15-rt19 compile error (was: realtime-preempt patch-2.6.15-rt18 issues) karsten wiese
2006-03-15 9:31 ` Ingo Molnar
2006-03-15 10:19 ` Jan Altenberg
2006-03-15 11:04 ` Ingo Molnar
2006-03-15 14:08 ` karsten wiese
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 17:15 Rui Nuno Capela
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=440D54F2.2080009@tglx.de \
--to=tb10alj@tglx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rncbc@rncbc.org \
/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