linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: si.yanteng@linux.dev
To: "Haoyang Liu" <tttturtleruss@hust.edu.cn>,
	"Alex Shi" <alexs@kernel.org>,
	"Yanteng Si" <siyanteng@loongson.cn>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"Bill Wendling" <morbo@google.com>,
	"Justin Stitt" <justinstitt@google.com>
Cc: hust-os-kernel-patches@googlegroups.com,
	"Haoyang Liu" <tttturtleruss@hust.edu.cn>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH v3] docs/zh_CN: Add dev-tools/kcsan Chinese translation
Date: Mon, 29 Jul 2024 08:32:13 +0000	[thread overview]
Message-ID: <ce5a146b8a1857fda90bce79934ae5f9ec2bfee9@linux.dev> (raw)
In-Reply-To: <20240727150844.6502-1-tttturtleruss@hust.edu.cn>

2024年7月27日 23:08, "Haoyang Liu" <tttturtleruss@hust.edu.cn> 写到:


Hi Haoyang,

> 
> Translate dev-tools/kcsan commit 31f605a308e6
> 
> ("kcsan, compiler_types: Introduce __data_racy type qualifier")
> 
> into Chinese and add it in dev-tools/zh_CN/index.rst
> 
> Signed-off-by: Haoyang Liu <tttturtleruss@hust.edu.cn>
> 
> ---
> 
> v2 -> v3: Revised some sentences based on reviewer's suggestions and updated the KTSAN url.
Our comments need a clear response, and I have noticed
that Alex has already commented on v3, so before sending
v4, you need to reply to each of his comments one by one.

BTW:
Because you have already sent v3, you don't need to reply to v2 anymore.


Thanks,
Yanteng

      parent reply	other threads:[~2024-07-29  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27 15:08 [PATCH v3] docs/zh_CN: Add dev-tools/kcsan Chinese translation Haoyang Liu
2024-07-28  4:17 ` Alex Shi
2024-07-29 12:56   ` Haoyang Liu
2024-07-30  1:21     ` Alex Shi
2024-07-30  1:38       ` Dongliang Mu
2024-07-30  1:48         ` Alex Shi
2024-07-31 11:16       ` Haoyang Liu
2024-07-29  8:32 ` si.yanteng [this message]

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=ce5a146b8a1857fda90bce79934ae5f9ec2bfee9@linux.dev \
    --to=si.yanteng@linux.dev \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=hust-os-kernel-patches@googlegroups.com \
    --cc=justinstitt@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=siyanteng@loongson.cn \
    --cc=tttturtleruss@hust.edu.cn \
    /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).