From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjan@infradead.org>,
Nicolas Pitre <nico@cam.org>,
Jes Sorensen <jes@trained-monkey.org>,
Al Viro <viro@ftp.linux.org.uk>, Oleg Nesterov <oleg@tv-sign.ru>,
David Howells <dhowells@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [patch 16/19] mutex subsystem, semaphore to completion: SX8
Date: Tue, 3 Jan 2006 13:38:23 +0100 [thread overview]
Message-ID: <20060103123823.GA13178@elte.hu> (raw)
In-Reply-To: <43BA6C96.2060305@yahoo.com.au>
* Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> Ingo Molnar wrote:
> >From: Steven Rostedt <rostedt@goodmis.org>
> >
> >change SX8 semaphores to completions.
> >
> >Signed-off-by: Ingo Molnar <mingo@elte.hu>
> >+#include <linux/completion.h>
> > #include <asm/io.h>
> > #include <asm/semaphore.h>
>
> These patches should remove the asm/semaphore.h when appropriate too.
> At a glance, this looks like one such case.
yeah, agreed. I did this in my tree. (the other sem2completion patches
are not affected)
> Also, these aren't really part of a mutex subsystem patch series are
> they?
i included them because they reduce the number of semaphores that are
used in a non-mutex fashion, and thus make the mutex conversion easier.
I.e. i consider both the sem2mutex and the sem2completion patches as
part of the 'convert semaphores to mutexes' effort, even though
sem2completions are independent technically. They can be applied
independently of the mutex subsystem itself, of course.
Ingo
next prev parent reply other threads:[~2006-01-03 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 10:09 Ingo Molnar
2006-01-03 12:22 ` Nick Piggin
2006-01-03 12:38 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-03 16:47 Ingo Molnar
2006-01-02 16:35 Ingo Molnar, Steven Rostedt
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=20060103123823.GA13178@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=nico@cam.org \
--cc=oleg@tv-sign.ru \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®