From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: dhowells@redhat.com, corbet@lwn.net, minchan@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Add Korean translation of memory-barriers.txt
Date: Wed, 9 Mar 2016 18:01:27 -0800 [thread overview]
Message-ID: <20160310020127.GE3452@linux.vnet.ibm.com> (raw)
In-Reply-To: <1457570939-7740-1-git-send-email-sj38.park@gmail.com>
On Thu, Mar 10, 2016 at 09:48:54AM +0900, SeongJae Park wrote:
> This patchset aims to add Korean translation of memory-barriers document.
>
> The patchset starts from fixing minor and trivial problems in the original
> document that found during translation. After that, the final patch adds the
> Korean translation of the document.
>
> The patches are based on recent next tree:
> 0f6dd067b9c3c712b1177fa2fc0deb21805c771c ("Add linux-next specific files for
> 20160309")
I have queued this series for review, thank you!
Of course, I cannot do anything to the Korean translation other than to
pass it through unchanged. ;-)
Thanx, Paul
> SeongJae Park (5):
> doc/memory-barriers: fix missed renaming: s/lock/acquire
> doc/memory-barriers: add missed subsection in TOC
> doc/memory-barriers: fix typo
> doc/memory-barriers: Insert white spaces consistently
> Doc/memory-barriers: add Korean translation
>
> Documentation/ko_KR/memory-barriers.txt | 3048 +++++++++++++++++++++++++++++++
> Documentation/memory-barriers.txt | 62 +-
> 2 files changed, 3081 insertions(+), 29 deletions(-)
> create mode 100644 Documentation/ko_KR/memory-barriers.txt
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-03-10 2:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 0:48 [PATCH 0/5] Add Korean translation of memory-barriers.txt SeongJae Park
2016-03-10 0:48 ` [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire SeongJae Park
2016-03-10 0:48 ` [PATCH 2/5] doc/memory-barriers: add missed subsection in TOC SeongJae Park
2016-03-10 0:48 ` [PATCH 3/5] doc/memory-barriers: fix typo SeongJae Park
2016-03-10 0:48 ` [PATCH 4/5] doc/memory-barriers: Insert white spaces consistently SeongJae Park
2016-03-10 0:48 ` [PATCH 5/5] Doc/memory-barriers: add Korean translation SeongJae Park
2016-03-10 2:01 ` Paul E. McKenney [this message]
2016-03-10 8:13 ` [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire David Howells
2016-03-10 8:50 ` SeongJae Park
2016-03-10 9:45 ` David Howells
2016-03-10 14:39 ` SeongJae Park
2016-03-10 8:14 ` [PATCH 4/5] doc/memory-barriers: Insert white spaces consistently David Howells
2016-03-10 8:15 ` [PATCH 3/5] doc/memory-barriers: fix typo David Howells
2016-03-10 8:16 ` [PATCH 2/5] doc/memory-barriers: add missed subsection in TOC David Howells
2016-03-10 8:17 ` [PATCH 5/5] Doc/memory-barriers: add Korean translation David Howells
2016-03-11 8:56 ` [PATCH 0/5] Add Korean translation of memory-barriers.txt Gioh Kim
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=20160310020127.GE3452@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sj38.park@gmail.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).