From: YanTeng Si <si.yanteng@linux.dev>
To: Haoyang Liu <tttturtleruss@hust.edu.cn>,
Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
Yanteng Si <siyanteng@loongson.cn>,
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,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v5] docs/zh_CN: Add dev-tools/kcsan Chinese translation
Date: Fri, 9 Aug 2024 18:57:11 +0800 [thread overview]
Message-ID: <2e27c607-713f-48f2-9a2e-41f7c61f7e73@linux.dev> (raw)
In-Reply-To: <25b4c3e0-784d-41ea-8ff3-8cb175983676@linux.dev>
在 2024/8/9 18:44, YanTeng Si 写道:
> Hi Haoyang,
>
> 在 2024/8/8 0:48, Haoyang Liu 写道:
>>
>> 在 2024/8/8 0:45, Jonathan Corbet 写道:
>>> Haoyang Liu <tttturtleruss@hust.edu.cn> writes:
>>>
>>>> This is a mistake but I missed it before sending this patch.
>>>>
>>>> What should I do to revert or correct this patch?
>>>>
>>>> Thanks for your help and patience.
>>> Send a v6 with the correction made - but wait a while for other reviews
>>> first.
>>
>> OK.
>>
> The doc is good enough for me, so you can send a v6 after fix the typo.
>
>
> Reviewed-by: Yanteng Si <siyanteng@loongson.cn>
I am Sorry! It seems that I've permanently lost access to
siyanteng@loongson.cn account,
So you need use --suppress-cc=sob when you send-email and pick my
Reviewed-by tag.
Thanks,
Yanteng
>
>
> Thanks,
>
> Yanteng
>
>>
>> Thank you,
>>
>> Haoyang
>>
>>>
>>> Thanks,
>>>
>>> jon
>>
>>
>
next prev parent reply other threads:[~2024-08-09 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 16:27 [PATCH v5] docs/zh_CN: Add dev-tools/kcsan Chinese translation Haoyang Liu
2024-08-07 16:41 ` Haoyang Liu
2024-08-07 16:45 ` Jonathan Corbet
2024-08-07 16:48 ` Haoyang Liu
2024-08-09 10:44 ` YanTeng Si
2024-08-09 10:57 ` YanTeng Si [this message]
2024-08-10 14:58 ` Haoyang Liu
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=2e27c607-713f-48f2-9a2e-41f7c61f7e73@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