From: SeongJae Park <sj38.park@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
"Paul E. McKenney" <paulmck@kernel.org>
Cc: Will Deacon <will@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>,
SeongJae Park <sjpark@amazon.de>
Subject: Re: [PATCH] docs/memory-barriers.txt.kokr: Minor wordsmith
Date: Fri, 6 Dec 2019 18:21:44 +0100 [thread overview]
Message-ID: <CAEjAshoczVRTavYmEb82xh+aJzQ30sKJRTuj=os7nZfFQ3AFfg@mail.gmail.com> (raw)
In-Reply-To: <20191129182823.8710-1-sjpark@amazon.de>
Hello Jon and Paul,
On Fri, Nov 29, 2019 at 7:29 PM SeongJae Park <sj38.park@gmail.com> wrote:
>
> As suggested by Paul, I got a review from another Korean hacker Yunjae.
> From the review, I got not only 'Reviewed-by:' tags, but also found a
> few minor nits. So I made a second version of the patchset but just
> realized that the first version has already sent to Linus. I therefore
> send only the nit fixes as another patch.
May I ask your comments?
Thanks,
SeongJae Park
>
> ----------------------------- >8 ----------------------------------------
> docs/memory-barriers.txt.kokr: Minor wordsmith
>
> This commit fixes a couple of minor nits in the Korean translation of
> 'memory-barriers.txt'.
>
> Signed-off-by: SeongJae Park <sjpark@amazon.de>
> Reviewed-by: Yunjae Lee <lyj7694@gmail.com>
> ---
> Documentation/translations/ko_KR/memory-barriers.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/translations/ko_KR/memory-barriers.txt b/Documentation/translations/ko_KR/memory-barriers.txt
> index a8d26df9360b..29e76a73ae59 100644
> --- a/Documentation/translations/ko_KR/memory-barriers.txt
> +++ b/Documentation/translations/ko_KR/memory-barriers.txt
> @@ -2413,7 +2413,7 @@ _않습니다_.
> 알고 있는, - inb() 나 writel() 과 같은 - 적절한 액세스 루틴을 통해 이루어져야만
> 합니다. 이것들은 대부분의 경우에는 명시적 메모리 배리어 와 함께 사용될 필요가
> 없습니다만, 완화된 메모리 액세스 속성으로 I/O 메모리 윈도우로의 참조를 위해
> -액세스 함수가 사용된다면 순서를 강제하기 위해 _madatory_ 메모리 배리어가
> +액세스 함수가 사용된다면 순서를 강제하기 위해 _mandatory_ 메모리 배리어가
> 필요합니다.
>
> 더 많은 정보를 위해선 Documentation/driver-api/device-io.rst 를 참고하십시오.
> @@ -2528,7 +2528,7 @@ I/O 액세스를 통한 주변장치와의 통신은 아키텍쳐와 기기에
> 이것들은 readX() 와 writeX() 랑 비슷하지만, 더 완화된 메모리 순서
> 보장을 제공합니다. 구체적으로, 이것들은 일반적 메모리 액세스나 delay()
> 루프 (예:앞의 2-5 항목) 에 대해 순서를 보장하지 않습니다만 디폴트 I/O
> - 기능으로 매핑된 __iomem 포인터에 대해 동작할 때, 같은 CPU 쓰레드에 의해
> + 기능으로 매핑된 __iomem 포인터에 대해 동작할 때, 같은 CPU 쓰레드에 의한
> 같은 주변장치로의 액세스에는 순서가 맞춰질 것이 보장됩니다.
>
> (*) readsX(), writesX():
> --
> 2.17.2
>
next prev parent reply other threads:[~2019-12-06 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 23:41 [PATCH 0/7] docs: Update ko_KR translations SeongJae Park
2019-11-21 23:41 ` [PATCH 1/7] docs/memory-barriers.txt/kokr: Rewrite "KERNEL I/O BARRIER EFFECTS" section SeongJae Park
2019-11-21 23:41 ` [PATCH 2/7] Documentation/kokr: Kill all references to mmiowb() SeongJae Park
2019-11-21 23:41 ` [PATCH 3/7] docs/memory-barriers.txt/kokr: Fix style, spacing and grammar in I/O section SeongJae Park
2019-11-21 23:41 ` [PATCH 4/7] docs/memory-barriers.txt/kokr: Update I/O section to be clearer about CPU vs thread SeongJae Park
2019-11-21 23:41 ` [PATCH 5/7] docs/memory-barriers.txt: Remove remaining references to mmiowb() SeongJae Park
2019-11-21 23:41 ` [PATCH 6/7] Documentation/translation: Use Korean for Korean translation title SeongJae Park
2019-11-21 23:41 ` [PATCH 7/7] Documentation/process/howto/kokr: Update for 4.x -> 5.x versioning SeongJae Park
2019-11-22 17:01 ` [PATCH 0/7] docs: Update ko_KR translations Jonathan Corbet
2019-11-26 22:21 ` Paul E. McKenney
2019-11-26 22:36 ` SeongJae Park
2019-11-27 14:12 ` Jonathan Corbet
2019-11-27 14:27 ` Paul E. McKenney
2019-11-29 18:28 ` [PATCH] docs/memory-barriers.txt.kokr: Minor wordsmith SeongJae Park
2019-12-06 17:21 ` SeongJae Park [this message]
2019-12-12 17:30 ` SeongJae Park
2019-12-19 16:41 ` Jonathan Corbet
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='CAEjAshoczVRTavYmEb82xh+aJzQ30sKJRTuj=os7nZfFQ3AFfg@mail.gmail.com' \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sjpark@amazon.de \
--cc=will@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 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).