From: Gang Li <gang.li@linux.dev>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-doc@vger.kernel.org, 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>, Boqun Feng <boqun.feng@gmail.com>,
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>,
Daniel Lustig <dlustig@nvidia.com>,
Joel Fernandes <joel@joelfernandes.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RESEND v1] docs/zh_CN: add zh_CN translation for memory-barriers.txt
Date: Mon, 14 Aug 2023 18:57:18 +0800 [thread overview]
Message-ID: <a308e43a-2561-3d2b-28c7-eb3fe73cd43a@linux.dev> (raw)
In-Reply-To: <479156cf-1bdb-421a-8dab-0db8ff73012b@loongson.cn>
Hi,
On 2023/8/14 15:58, Yanteng Si wrote:
> [PATCH v2 1/2] docs: convert memory-barriers.txt to RST
>
We already have a wrapper loading memory-barriers.txt into html:
https://www.kernel.org/doc/html/latest/core-api/wrappers/memory-barriers.html
Thanks,
Gang Li
next prev parent reply other threads:[~2023-08-14 10:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 8:08 [PATCH RESEND v1] docs/zh_CN: add zh_CN translation for memory-barriers.txt Gang Li
2023-08-12 11:00 ` Yanteng Si
2023-08-14 2:40 ` Gang Li
2023-08-14 7:58 ` Yanteng Si
2023-08-14 10:57 ` Gang Li [this message]
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=a308e43a-2561-3d2b-28c7-eb3fe73cd43a@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 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.