Re: [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire

[SeongJae Park]

On Thu, Mar 10, 2016 at 6:45 PM, David Howells <dhowells@xxxxxxxxxx> wrote:
> SeongJae Park <sj38.park@xxxxxxxxx> wrote:
>
>> >> -     - Locking functions.
>> >> +     - Acquiring functions.
>> ...
>> > 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.
>
> Whilst that's true, most people think of them as locks.  You could change the
> name of the section to:
>
>         Locking/Acquiring functions
>
> or:
>
>         Lock acquisition functions

Thank you for your suggestion, David.  I will send new patchset ASAP.

Thanks,
SeongJae Park

>
> perhaps.
>
> David