From: SeongJae Park <sj38.park@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: SeongJae Park <sj38.park@gmail.com>,
paulmck@linux.vnet.ibm.com, corbet@lwn.net, minchan@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire
Date: Thu, 10 Mar 2016 17:50:49 +0900 (KST) [thread overview]
Message-ID: <alpine.DEB.2.10.1603101739310.16296@hxeon> (raw)
In-Reply-To: <30258.1457597615@warthog.procyon.org.uk>
On Thu, 10 Mar 2016, David Howells wrote:
> SeongJae Park <sj38.park@gmail.com> wrote:
>
>> - - Locking functions.
>> + - Acquiring functions.
>
> Actually, this should be 'locking' functions. If you look at the text:
>
> ACQUIRING FUNCTIONS
> -------------------
>
> The Linux kernel has a number of locking constructs:
>
> (*) spin locks
> (*) R/W spin locks
> (*) mutexes
> (*) semaphores
> (*) R/W semaphores
>
> It's specifically talking about locking functions that the kernel provides -
> or are we calling the spin acquires and R/W spin acquires now? "Locking" is
> the key that people referring to the document are going to use.
AFAIU, the next line of the quoted text says the section is talking about
variants on "ACQUIRE" operations and "RELEASE" operations for each locking
constructs. I thought the original change which changed the name of
section has made full consensus and I am just want to make the section
names in `Contents` section and its real section name. I will listen to
other's opinions more.
Thanks,
SeongJae Park
>
> David
>
next prev parent reply other threads:[~2016-03-10 8:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 0:48 [PATCH 0/5] Add Korean translation of memory-barriers.txt SeongJae Park
2016-03-10 0:48 ` [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire SeongJae Park
2016-03-10 0:48 ` [PATCH 2/5] doc/memory-barriers: add missed subsection in TOC SeongJae Park
2016-03-10 0:48 ` [PATCH 3/5] doc/memory-barriers: fix typo SeongJae Park
2016-03-10 0:48 ` [PATCH 4/5] doc/memory-barriers: Insert white spaces consistently SeongJae Park
2016-03-10 0:48 ` [PATCH 5/5] Doc/memory-barriers: add Korean translation SeongJae Park
2016-03-10 2:01 ` [PATCH 0/5] Add Korean translation of memory-barriers.txt Paul E. McKenney
2016-03-10 8:13 ` [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire David Howells
2016-03-10 8:50 ` SeongJae Park [this message]
2016-03-10 9:45 ` David Howells
2016-03-10 14:39 ` SeongJae Park
2016-03-10 8:14 ` [PATCH 4/5] doc/memory-barriers: Insert white spaces consistently David Howells
2016-03-10 8:15 ` [PATCH 3/5] doc/memory-barriers: fix typo David Howells
2016-03-10 8:16 ` [PATCH 2/5] doc/memory-barriers: add missed subsection in TOC David Howells
2016-03-10 8:17 ` [PATCH 5/5] Doc/memory-barriers: add Korean translation David Howells
2016-03-11 8:56 ` [PATCH 0/5] Add Korean translation of memory-barriers.txt Gioh Kim
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=alpine.DEB.2.10.1603101739310.16296@hxeon \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).