From: Minchan Kim <minchan@kernel.org>
To: SeongJae Park <sj38.park@gmail.com>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
David Howells <dhowells@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] Add Korean translation of memory-barriers.txt
Date: Tue, 15 Mar 2016 08:36:05 +0900 [thread overview]
Message-ID: <20160314233605.GA17980@bbox> (raw)
In-Reply-To: <CAEjAshq9F_6KofVQhO-JwfREU3riONwgTVuz4SzRJAnbFpWLyA@mail.gmail.com>
On Tue, Mar 15, 2016 at 06:52:11AM +0900, SeongJae Park wrote:
> On Tue, Mar 15, 2016 at 5:17 AM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> > On Fri, Mar 11, 2016 at 12:06:55AM +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")
> >
> > Queued, thank you! I am going to have to trust you on the Korean, good
> > thing you list yourself as maintainer. ;-)
>
> Thank you, Paul! I believe this change may help future Korean hackers. Also,
> I will do my best to maintain the document up to date with good quality.
+1
I cannot expect when someone who knows Korean, understand memory-barrier stuff
very well and have enough time to reivew comes up. Anyway, if the translation
has a problem, we could fix it later so I really appreciate SeongJae's nice
contribution translated one of hardest document but valuable.
Acked-by: Minchan Kim <minchan@kernel.org>
next prev parent reply other threads:[~2016-03-14 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 15:06 [PATCH v2 0/5] Add Korean translation of memory-barriers.txt SeongJae Park
2016-03-10 15:06 ` [PATCH v2 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire SeongJae Park
2016-03-10 15:06 ` [PATCH v2 2/5] doc/memory-barriers: add missed subsection in TOC SeongJae Park
2016-03-10 15:06 ` [PATCH v2 3/5] doc/memory-barriers: fix typo SeongJae Park
2016-03-10 15:06 ` [PATCH v2 4/5] doc/memory-barriers: Insert white spaces consistently SeongJae Park
2016-03-10 15:07 ` [PATCH v2 5/5] Doc/memory-barriers: add Korean translation SeongJae Park
2016-03-14 20:17 ` [PATCH v2 0/5] Add Korean translation of memory-barriers.txt Paul E. McKenney
2016-03-14 21:52 ` SeongJae Park
2016-03-14 23:36 ` Minchan Kim [this message]
2016-03-14 23:55 ` 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=20160314233605.GA17980@bbox \
--to=minchan@kernel.org \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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 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.