From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org, corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, SeongJae Park <sj@kernel.org>
Subject: [PATCH 0/4] docs/memory-barriers.txt: Fix nits and update Korean translation
Date: Sat, 8 Oct 2022 10:49:24 -0700 [thread overview]
Message-ID: <20221008174928.13479-1-sj@kernel.org> (raw)
This patchset fixes one trivial nit in memory-barriers.txt (patch 1) and
updates Korean translation to match the content of the original one
(patches 2-4).
SeongJae Park (4):
docs/memory-barriers.txt: Add a missed closing parenthesis
docs/memory-barriers.txt/kokr: introduce io_stop_wc() and add
implementation for ARM64
docs/memory-barriers.txt/kokr: Add memory barrier dma_mb()
docs/memory-barriers.txt/kokr: Fix confusing name of 'data dependency
barrier'
Documentation/memory-barriers.txt | 2 +-
.../translations/ko_KR/memory-barriers.txt | 149 ++++++++++--------
2 files changed, 86 insertions(+), 65 deletions(-)
--
2.17.1
next reply other threads:[~2022-10-08 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 17:49 SeongJae Park [this message]
2022-10-08 17:49 ` [PATCH 1/4] docs/memory-barriers.txt: Add a missed closing parenthesis SeongJae Park
2022-10-09 2:04 ` Bagas Sanjaya
2022-10-09 11:10 ` Paul E. McKenney
2022-10-09 18:37 ` SeongJae Park
2022-10-11 2:47 ` SeongJae Park
2022-10-08 17:49 ` [PATCH 2/4] docs/memory-barriers.txt/kokr: introduce io_stop_wc() and add implementation for ARM64 SeongJae Park
2022-10-08 17:49 ` [PATCH 3/4] docs/memory-barriers.txt/kokr: Add memory barrier dma_mb() SeongJae Park
2022-10-08 17:49 ` [PATCH 4/4] docs/memory-barriers.txt/kokr: Fix confusing name of 'data dependency barrier' SeongJae Park
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=20221008174928.13479-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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 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).