From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org, corbet@lwn.net
Cc: lyj7694@gmail.com, linux-doc@vger.kernel.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
SeongJae Park <sj@kernel.org>
Subject: [PATCH v2 0/3] docs/memory-barriers/kokr: Update the content
Date: Mon, 10 Oct 2022 19:58:06 -0700 [thread overview]
Message-ID: <20221011025809.25821-1-sj@kernel.org> (raw)
There are updates to memory-barriers.txt that not applied to the Korean
translation. This patchset applies the changes.
Changes from v1
(https://lore.kernel.org/all/20221008174928.13479-1-sj@kernel.org/)
- Drop first one, which is not for translation and already pulled
- Use better expressions for Korean (Yunjae Lee)
- Fix a typo (Yunjae Lee)
SeongJae Park (3):
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'
.../translations/ko_KR/memory-barriers.txt | 149 ++++++++++--------
1 file changed, 85 insertions(+), 64 deletions(-)
--
2.17.1
next reply other threads:[~2022-10-11 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 2:58 SeongJae Park [this message]
2022-10-11 2:58 ` [PATCH v2 1/3] docs/memory-barriers.txt/kokr: introduce io_stop_wc() and add implementation for ARM64 SeongJae Park
2022-10-11 2:58 ` [PATCH v2 2/3] docs/memory-barriers.txt/kokr: Add memory barrier dma_mb() SeongJae Park
2022-10-11 2:58 ` [PATCH v2 3/3] docs/memory-barriers.txt/kokr: Fix confusing name of 'data dependency barrier' SeongJae Park
2022-10-12 6:16 ` [PATCH v2 0/3] docs/memory-barriers/kokr: Update the content Paul E. McKenney
[not found] ` <CAE+zRGXBOyyvDsPYVAVwuKT1NzAKgoR939SUu6X5LnhXOUzqyA@mail.gmail.com>
2022-10-13 6:18 ` Paul E. McKenney
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=20221011025809.25821-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=lyj7694@gmail.com \
--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 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.