From: Ingo Molnar <mingo@kernel.org>
To: Byungchul Park <byungchul.park@lge.com>
Cc: SeongJae Park <sj38.park@gmail.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
David Howells <dhowells@redhat.com>,
Minchan Kim <minchan@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v4 3/3] Doc/memory-barriers: Add Korean translation
Date: Fri, 8 Jul 2016 12:13:27 +0200 [thread overview]
Message-ID: <20160708101327.GB20765@gmail.com> (raw)
In-Reply-To: <20160708011754.GI2279@X58A-UD3R>
* Byungchul Park <byungchul.park@lge.com> wrote:
> On Fri, Jul 08, 2016 at 07:50:39AM +0900, SeongJae Park wrote:
> > > I will add my opinion in korean.
> >
> > Thank you for kind and faithful review. I agree with most of your opinions and
> > suggestions. Most of your suggestions looks much better than mine.
> >
> > However, I also have some different opinion. I want to emphasize the fact that
> > (1) CPUs 'issue' memory operations to memory system as they want, (2) memory
> > system 'executes' those operations as they want, and (3) CPUs 'perceive' the
> > 'effects' of the operation executions as they want. I want to emphasize the
> > fact in document because I think most confusion about memory ordering comes
> > from vague understanding about the relation. To my perspective, few of your
>
> Right. I agree with you.
Do these vague formulations exist in the English text as well? If yes then please
try to improve the English text first, then do the Korean translation.
Thanks,
Ingo
next prev parent reply other threads:[~2016-07-08 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 23:27 [PATCH v4 0/3] Doc/memory-barriers: Add Korean translation SeongJae Park
2016-07-03 23:27 ` [PATCH v4 1/3] memory-barriers.txt: maintain consistent blank line SeongJae Park
2016-07-03 23:27 ` [PATCH v4 2/3] memory-barriers.txt: fix wrong section reference SeongJae Park
2016-07-03 23:27 ` [PATCH v4 3/3] Doc/memory-barriers: Add Korean translation SeongJae Park
2016-07-05 12:34 ` Byungchul Park
2016-07-05 21:57 ` SeongJae Park
2016-07-07 12:00 ` Byungchul Park
2016-07-07 22:50 ` SeongJae Park
2016-07-08 1:17 ` Byungchul Park
2016-07-08 10:13 ` Ingo Molnar [this message]
2016-07-08 10:22 ` SeongJae Park
2016-07-05 21:36 ` [PATCH v4 0/3] " Paul E. McKenney
2016-07-05 22:11 ` 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=20160708101327.GB20765@gmail.com \
--to=mingo@kernel.org \
--cc=byungchul.park@lge.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=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 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).