From: Ingo Oeser <ioe-lkml@rameria.de>
To: linux-kernel@vger.kernel.org, chaosite@gmail.com
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Arjan van de Ven <arjan@infradead.org>,
Jes Sorensen <jes@trained-monkey.org>, Greg KH <greg@kroah.com>
Subject: Re: [patch 00/62] sem2mutex: -V1
Date: Sat, 14 Jan 2006 14:22:10 +0100 [thread overview]
Message-ID: <200601141422.16760.ioe-lkml@rameria.de> (raw)
In-Reply-To: <43C815E3.10005@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
On Friday 13 January 2006 22:04, Matan Peled wrote:
> Ingo Molnar wrote:
> > Ingo Oeser wrote:
> >> Could we get for each of these and a mutex:
> >>
> >> - description
> >> - common use case
> >> - small argument why this and nothing else should be used there
> >
> > like ... Documentation/mutex-design.txt?
>
> I think what he wanted was an explanation for the change of each and every
> sem... Which is kind of hard with automated tools.
No this is too much! I wouldn't expect this.
Just example conversions for each 3 conversion types with full discussion
(or discussion at all) like we do for all other patches would be enough.
semaphore -> mutex is explained a bit in Documentation/mutex-design.txt
Still missing:
- semaphore -> completion
- semaphore -> struct work
Regards
Ingo Oeser
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-14 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 12:44 Ingo Molnar
2006-01-13 12:59 ` Duncan Sands
2006-01-13 13:06 ` Arjan van de Ven
2006-01-13 13:44 ` Ingo Molnar
2006-01-13 18:25 ` Ingo Oeser
2006-01-13 19:56 ` Ingo Molnar
2006-01-13 21:04 ` Matan Peled
2006-01-13 21:25 ` Arjan van de Ven
2006-01-13 22:09 ` Junio C Hamano
2006-01-13 22:13 ` Arjan van de Ven
2006-01-14 13:22 ` Ingo Oeser [this message]
2006-01-14 13:49 ` Thomas Gleixner
2006-01-14 13:16 ` Ingo Oeser
2006-01-14 13:31 ` Arjan van de Ven
2006-01-14 13:38 ` Ingo Molnar
2006-01-13 13:23 ` Ingo Molnar
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=200601141422.16760.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=chaosite@gmail.com \
--cc=greg@kroah.com \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®