From: SeongJae Park <sj38.park@gmail.com>
To: corbet@lwn.net, paulmck@kernel.org
Cc: SeongJae Park <sjpark@amazon.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/5] docs/locking: Fix outdated section names
Date: Fri, 31 Jan 2020 21:52:33 +0100 [thread overview]
Message-ID: <20200131205237.29535-2-sj38.park@gmail.com> (raw)
In-Reply-To: <20200131205237.29535-1-sj38.park@gmail.com>
From: SeongJae Park <sjpark@amazon.com>
Commit 2e4f5382d12a ("locking/doc: Rename LOCK/UNLOCK to
ACQUIRE/RELEASE") has not appied to 'spinlock.rst'. This commit updates
the doc for the change.
Signed-off-by: SeongJae Park <sjpark@amazon.com>
---
Documentation/locking/spinlocks.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/locking/spinlocks.rst b/Documentation/locking/spinlocks.rst
index 66e3792f8a36..bec96f7a9f2d 100644
--- a/Documentation/locking/spinlocks.rst
+++ b/Documentation/locking/spinlocks.rst
@@ -25,9 +25,9 @@ worry about UP vs SMP issues: the spinlocks work correctly under both.
Documentation/memory-barriers.txt
- (5) LOCK operations.
+ (5) ACQUIRE operations.
- (6) UNLOCK operations.
+ (6) RELEASE operations.
The above is usually pretty simple (you usually need and want only one
spinlock for most things - using more than one spinlock can make things a
--
2.17.1
next prev parent reply other threads:[~2020-01-31 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 20:52 [PATCH 0/5] Documentation: Fix trivial nits SeongJae Park
2020-01-31 20:52 ` SeongJae Park [this message]
2020-01-31 20:52 ` [PATCH 2/5] docs/ko_KR/howto: Insert missing dots SeongJae Park
2020-02-05 17:15 ` Jonathan Corbet
2020-02-06 0:12 ` SeongJae Park
2020-01-31 20:52 ` [PATCH 3/5] Documentation/ko_KR/howto: Update broken web addresses SeongJae Park
2020-01-31 20:52 ` [PATCH 4/5] Documentation/ko_KR/howto: Update a broken link SeongJae Park
2020-01-31 20:52 ` [PATCH 5/5] Documentation/memory-barriers: Fix typos SeongJae Park
2020-01-31 21:23 ` Paul E. McKenney
2020-02-05 17:22 ` [PATCH 0/5] Documentation: Fix trivial nits Jonathan Corbet
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=20200131205237.29535-2-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sjpark@amazon.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).