From: Arjan van de Ven <arjanv@redhat.com>
To: Paul Menage <menage@google.com>
Cc: arjanv@redhat.com, agrover@groveronline.com,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: ACPI global lock macros
Date: Tue, 9 Dec 2003 10:43:56 +0100 [thread overview]
Message-ID: <20031209094356.GA19702@devserv.devel.redhat.com> (raw)
In-Reply-To: <3FD5990A.9020908@google.com>
On Tue, Dec 09, 2003 at 01:42:34AM -0800, Paul Menage wrote:
> Arjan van de Ven wrote:
> >
> >maybe the odd thing is that it exists at all?
> >(eg why does ACPI need to have it's own locking primitives...)
>
> Because the ACPI spec defines its own locking protocol for
> synchronization between the OS and the BIOS.
... which can't be written based on linux locks ?
next prev parent reply other threads:[~2003-12-09 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 9:22 ACPI global lock macros Paul Menage
2003-12-09 9:36 ` Arjan van de Ven
2003-12-09 9:42 ` Paul Menage
2003-12-09 9:43 ` Arjan van de Ven [this message]
2003-12-09 9:50 ` Paul Menage
2003-12-10 7:45 ` [ACPI] " Andi Kleen
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=20031209094356.GA19702@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=agrover@groveronline.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
/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