From: Roger Larsson <roger.larsson@norran.net>
To: Nigel Gamble <nigel@nrg.org>, linux-kernel@vger.kernel.org
Cc: linux-audio-dev@ginette.musique.umontreal.ca
Subject: [PATCH] Re: [PATCH] Latest preemptible kernel (low latency) patch available
Date: Sat, 25 Nov 2000 00:49:57 +0100 [thread overview]
Message-ID: <00112500495700.06800@dox> (raw)
In-Reply-To: <Pine.LNX.4.05.10011221551330.19078-100000@cosmic.nrg.org>
In-Reply-To: <Pine.LNX.4.05.10011221551330.19078-100000@cosmic.nrg.org>
Hi,
I got compilation errors due to use of START / STOP
definitions (zlib.c, ppp?)
This little additional patch should fix it. They were not
used in any other place of the patch...
I am still compiling...
/RogerL
--- spinlock.h.preemt Sat Nov 25 00:31:38 2000
+++ spinlock.h Sat Nov 25 00:30:50 2000
@@ -47,21 +47,21 @@
/*
* Here are the basic preemption lock macros.
*/
-#define START 0
-#define STOP 1
-#define BKL ((((pree)current)->lock_depth) != -1)
+#define PREEMPT_START 0
+#define PREEMPT_STOP 1
+#define PREEMPT_BKL ((((pree)current)->lock_depth) != -1)
#ifdef DEBUG_PREEMPT
#define debug_lock(t) do { \
- if ((in_ctx_sw_off() - (BKL?1:0)) < t) \
+ if ((in_ctx_sw_off() - (PREEMPT_BKL?1:0))
< t) \
SPIN_BREAKPOINT; \
} while (0)
#else
#define debug_lock(t) do { } while (0)
#endif
-#define preempt_lock_start(c) debug_lock(START)
-#define preempt_lock_stop() debug_lock(STOP)
+#define preempt_lock_start(c) debug_lock(PREEMPT_START)
+#define preempt_lock_stop() debug_lock(PREEMPT_STOP)
#ifdef CONFIG_PREEMPT
#include <asm/current.h>
--
Home page:
http://www.norran.net/nra02596/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-25 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 0:04 [PATCH] Latest preemptible kernel (low latency) patch available Nigel Gamble
2000-11-24 23:49 ` Roger Larsson [this message]
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=00112500495700.06800@dox \
--to=roger.larsson@norran.net \
--cc=linux-audio-dev@ginette.musique.umontreal.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nrg.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;
as well as URLs for NNTP newsgroup(s).