From: Keith Owens <kaos@ocs.com.au>
To: George Anzinger <george@mvista.com>
Cc: John Kacur <jkacur@home.com>, linux-kernel@vger.kernel.org
Subject: Re: test11-pre2 compile error undefined reference to `bust_spinlocks' WHAT?!
Date: Sat, 11 Nov 2000 04:34:06 +1100 [thread overview]
Message-ID: <7834.973877646@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 10 Nov 2000 09:15:54 -0800." <3A0C2D4A.83C75D4B@mvista.com>
On Fri, 10 Nov 2000 09:15:54 -0800,
George Anzinger <george@mvista.com> wrote:
>The notion of releasing a spin lock by initializing it seems IMHO, on
>the face of it, way off.
Normally it would be, but these are NMI and panic messages. The system
is pretty dead at that point, getting the message out is deemed more
important than maintaining the spinlock. BTW, bust_spinlocks is not my
idea, please direct any queries to Andrew Morton. I just fixed a link
error.
-
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/
next prev parent reply other threads:[~2000-11-10 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 5:32 test11-pre2 compile error undefined reference to `bust_spinlocks' John Kacur
2000-11-10 4:57 ` Keith Owens
2000-11-10 5:07 ` Jeff Garzik
2000-11-10 5:08 ` Keith Owens
2000-11-10 17:15 ` test11-pre2 compile error undefined reference to `bust_spinlocks' WHAT?! George Anzinger
2000-11-10 17:34 ` Keith Owens [this message]
2000-11-11 0:21 ` Andrew Morton
2000-11-11 8:50 ` Eric W. Biederman
2000-11-13 17:47 ` George Anzinger
2000-11-10 5:18 ` [patch] Re: test11-pre2 compile error undefined reference to `bust_spinlocks' Andrew Morton
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=7834.973877646@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=george@mvista.com \
--cc=jkacur@home.com \
--cc=linux-kernel@vger.kernel.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