From: Daniel Walker <dwalker@mvista.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
len.brown@intel.com, ak@linux.intel.com
Subject: Re: [PATCH 2/3] acpi: semaphore removal
Date: Sun, 20 Jul 2008 07:49:02 -0700 [thread overview]
Message-ID: <1216565342.3978.166.camel@localhost.localdomain> (raw)
In-Reply-To: <20080720081512.GC5947@disturbed>
On Sun, 2008-07-20 at 18:15 +1000, Dave Chinner wrote:
> On Sat, Jul 19, 2008 at 11:16:53AM -0700, Daniel Walker wrote:
> > The semaphore is used pretty extensively in acpi, but the actual
> > usage model is really more like completions. The ASL functions
> > getting implemented here are signals which follow a "wait for",
> > signaled, or rest format.
> >
> > This implements the ACPI signaling methods with the Linux
> > completion API, instead of using semaphores.
> >
> > completion_done() taken from Dave Chinner.
>
> The patch series that contained completion_done() is (AFAIK)
> in the -mm tree at the moment. You'd probably do best to keep
> it as a separate patch in your series so we don't end up with
> random conflicts all over the place....
Yeah, I will eventually pull it out .. I'm not too worried about it,
since these patches are a ways from even going into -mm ..
Daniel
next prev parent reply other threads:[~2008-07-20 14:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 18:16 [PATCH 0/3] acpi: acpi: sem out, mutex/completion in Daniel Walker
2008-07-19 18:16 ` [PATCH 1/3] acpi: add real mutex function calls Daniel Walker
2008-07-19 18:16 ` [PATCH 2/3] acpi: semaphore removal Daniel Walker
2008-07-19 18:16 ` [PATCH 3/3] Add lockdep integration for the ACPI mutex usage Daniel Walker
2008-07-20 8:15 ` [PATCH 2/3] acpi: semaphore removal Dave Chinner
2008-07-20 14:49 ` Daniel Walker [this message]
2008-07-21 1:51 ` [PATCH 1/3] acpi: add real mutex function calls Zhao Yakui
2008-07-21 9:14 ` Peter Zijlstra
2008-07-21 9:17 ` Andi Kleen
2008-07-21 9:24 ` Peter Zijlstra
2008-07-21 19:15 ` Andi Kleen
2008-07-21 19:33 ` Peter Zijlstra
2008-07-21 19:55 ` Matthew Wilcox
2008-07-21 20:22 ` Daniel Walker
2008-07-21 20:00 ` Andi Kleen
2008-07-21 20:38 ` Daniel Walker
2008-07-21 13:59 ` Daniel Walker
2008-07-21 13:56 ` Daniel Walker
2008-07-21 19:20 ` Andi Kleen
2008-07-21 19:39 ` Daniel Walker
2008-07-23 22:14 ` Moore, Robert
2008-07-24 12:44 ` 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=1216565342.3978.166.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=ak@linux.intel.com \
--cc=david@fromorbit.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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