From: Andi Kleen <ak@linux.intel.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Len Brown <len.brown@intel.com>,
Robert Moore <robert.moore@intel.com>
Subject: Re: [PATCH 4/4] acpi: semaphore removal
Date: Sat, 16 Aug 2008 00:17:46 +0200 [thread overview]
Message-ID: <48A6008A.8080104@linux.intel.com> (raw)
In-Reply-To: <1218831242-27618-5-git-send-email-dwalker@mvista.com>
Daniel Walker wrote:
> The semaphore usage in ACPI is more like completions. The ASL
> functions getting implemented here are signals which follow a
> "wait for", signaled, or reset format.
>
> This implements the ACPI signaling methods with the Linux
> completion API, instead of using semaphores.
NACK. I don't see the point of emulating semaphores when
there are already perfectly fine semaphores available.
-Andi
next prev parent reply other threads:[~2008-08-15 22:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 20:14 [PATCH 0/4] acpi semaphore removal v3 Daniel Walker
2008-08-15 20:14 ` [PATCH 1/4] add mutex_lock_timeout() Daniel Walker
2008-08-15 20:14 ` [PATCH 2/4] acpi: add real mutex function calls Daniel Walker
2008-08-15 20:14 ` [PATCH 3/4] acpi: add lockdep magic Daniel Walker
2008-08-15 20:14 ` [PATCH 4/4] acpi: semaphore removal Daniel Walker
2008-08-15 22:17 ` Andi Kleen [this message]
2008-08-16 0:18 ` Daniel Walker
2008-08-16 2:06 ` Andi Kleen
2008-08-16 4:15 ` Daniel Walker
2008-08-15 22:16 ` [PATCH 2/4] acpi: add real mutex function calls Andi Kleen
2008-08-15 23:10 ` Daniel Walker
2008-08-16 2:16 ` Andi Kleen
2008-08-16 4:11 ` Daniel Walker
-- strict thread matches above, loose matches on Subject: below --
2008-08-26 18:59 [PATCH 1/4] mutex: add mutex_lock_timeout() Daniel Walker
2008-08-26 18:59 ` [PATCH 2/4] acpi: add real mutex function calls Daniel Walker
2008-08-26 18:59 ` [PATCH 3/4] acpi: add lockdep magic Daniel Walker
2008-08-26 18:59 ` [PATCH 4/4] acpi: semaphore removal Daniel Walker
2008-08-26 19:13 ` Matthew Wilcox
2008-08-26 19:30 ` Daniel Walker
2008-08-26 19:50 ` Matthew Wilcox
2008-08-26 20:03 ` Daniel Walker
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=48A6008A.8080104@linux.intel.com \
--to=ak@linux.intel.com \
--cc=dwalker@mvista.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.moore@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.