From: Arjan van de Ven <arjan@infradead.org>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Dave Chinner <david@fromorbit.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] async: Add some documentation.
Date: Mon, 19 Jan 2009 04:52:42 -0800 [thread overview]
Message-ID: <20090119045242.73ba210f@infradead.org> (raw)
In-Reply-To: <20090119132744.0beee067@gondolin>
On Mon, 19 Jan 2009 13:27:44 +0100
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> > >
> > > I had it as that at first. But it is ugly; naming a function
> > > after its arguments is useless; it should be named after what it
> > > does instead.
> > >
> > > I buy that "special" is not a good name. Would "local" be better?
> > > The name needs to convey that it is for a specific synchronization
> > > context....
> >
> > Yeah, local is sounds ok - it's certainly more obvious
> > that it's a scope modifier for the synchronisation primitive.
>
> Hm, I don't like _local too much. How about _subset, or _context, or
> _scope?
or _domain ?
and phrase stuff such that you have synchronization domains?
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-01-19 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 16:43 [PATCH 2/2] async: Add some documentation Cornelia Huck
2009-01-13 20:36 ` Arjan van de Ven
2009-01-14 2:49 ` Dave Chinner
2009-01-14 10:24 ` Cornelia Huck
2009-01-19 0:39 ` Arjan van de Ven
2009-01-19 4:40 ` Dave Chinner
2009-01-19 12:27 ` Cornelia Huck
2009-01-19 12:52 ` Arjan van de Ven [this message]
2009-01-19 13:09 ` Cornelia Huck
2009-01-20 14:31 ` [PATCH] async: Rename _special -> _domain for clarity Cornelia Huck
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=20090119045242.73ba210f@infradead.org \
--to=arjan@infradead.org \
--cc=cornelia.huck@de.ibm.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.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 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.