From: Gang Li <gang.li@linux.dev>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: linux-arch@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Andrea Parri <parri.andrea@gmail.com>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>, Alex Shi <alexs@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
"Paul E. McKenney" <paulmck@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
Joel Fernandes <joel@joelfernandes.org>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH RESEND v1] docs/zh_CN: add zh_CN translation for memory-barriers.txt
Date: Mon, 14 Aug 2023 10:40:44 +0800 [thread overview]
Message-ID: <f8de40bf-1743-793f-7723-232adbfab623@linux.dev> (raw)
In-Reply-To: <2f519a69-8f12-4c07-bf20-6776a5ada256@loongson.cn>
Hi,
On 2023/8/12 19:00, Yanteng Si wrote:
> 在 2023/8/11 16:08, Gang Li 写道:
>> +译注:
>> +本文仅为方便汉语阅读,不保证与英文版本同步;
>> +若有疑问,请阅读英文版本;
>> +若有翻译问题,请通知译者;
>> +若想修改文档,也请先修改英文版本。
>
> In fact, we already have an easier way to do this, just include
> disclaimer-zh_CN.
>
> If you observe the files under .../zh_CN/, they all have a similar
> header, and we can completely follow them.
>
Thanks. I just noticed that there are txt files under
"zh_CN/arch/arm64/" and "zh_CN/video4linux/". They have the same header,
and I will
refer to them in v2.
> But you should also have noticed that memory-barriers are not a standard
> rst file and will not be built, which will result in it only staying in
> the development tree.
> It won't appear at:
https://docs.kernel.org
https://www.kernel.org/doc/html/latest/
But people can still access the txt document in this way:
https://www.kernel.org/doc/Documentation/memory-barriers.txt
> Finally, this patch is too huge and we may need some time to review it.
>
Of course. Would it be more convenient if I split the file into multiple
patches and send them as one series?
>
> Thanks,
>
> Yanteng
>
Thanks,
Gang Li
next prev parent reply other threads:[~2023-08-14 2:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 8:08 Gang Li
2023-08-12 11:00 ` Yanteng Si
2023-08-14 2:40 ` Gang Li [this message]
2023-08-14 7:58 ` Yanteng Si
2023-08-14 10:57 ` Gang Li
2023-08-14 12:50 ` Jonathan Corbet
2023-08-14 13:14 ` Yanteng Si
2023-08-14 14:31 ` Gang Li
2023-08-15 4:02 ` Patrick Yingxi Pan
2023-08-15 6:37 ` Gang Li
2023-08-15 11:08 ` Patrick Yingxi Pan
2023-08-15 14:28 ` Paul E. McKenney
2023-08-16 3:06 ` Yanteng Si
2023-08-17 3:03 ` Gang Li
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=f8de40bf-1743-793f-7723-232adbfab623@linux.dev \
--to=gang.li@linux.dev \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=siyanteng@loongson.cn \
--cc=stern@rowland.harvard.edu \
--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