linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 0/5] memory-barriers.txt: Applies upstream changes to the Korean version
Date: Tue,  3 Apr 2018 18:20:22 +0900	[thread overview]
Message-ID: <20180403092027.13471-1-sj38.park@gmail.com> (raw)

This patchset applies upstream changes for memory-barriers.txt to the Korean
version of it.

SeongJae Park (5):
  kokr/doc: READ_ONCE() now implies smp_barrier_depends()
  kokr/doc: De-emphasize smp_read_barrier_depends
  kokr/Documentation/memory-barriers.txt: Cross-reference
    "tools/memory-model/"
  kokr/memory-barriers: Fix description of data dependency barriers
  kokr/locking/memory-barriers: De-emphasize smp_read_barrier_depends()
    some more

 .../translations/ko_KR/memory-barriers.txt         | 50 +++++++++++++++-------
 1 file changed, 34 insertions(+), 16 deletions(-)

-- 
2.13.0

             reply	other threads:[~2018-04-03  9:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03  9:20 SeongJae Park [this message]
2018-04-03  9:20 ` [PATCH 1/5] kokr/doc: READ_ONCE() now implies smp_barrier_depends() SeongJae Park
2018-04-03  9:20 ` [PATCH 2/5] kokr/doc: De-emphasize smp_read_barrier_depends SeongJae Park
2018-04-03  9:20 ` [PATCH 3/5] kokr/Documentation/memory-barriers.txt: Cross-reference "tools/memory-model/" SeongJae Park
2018-04-03  9:20 ` [PATCH 4/5] kokr/memory-barriers: Fix description of data dependency barriers SeongJae Park
2018-04-03  9:20 ` [PATCH 5/5] kokr/locking/memory-barriers: De-emphasize smp_read_barrier_depends() some more SeongJae Park
2018-04-03 17:14 ` [PATCH 0/5] memory-barriers.txt: Applies upstream changes to the Korean version 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=20180403092027.13471-1-sj38.park@gmail.com \
    --to=sj38.park@gmail.com \
    --cc=linux-kernel@vger.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).