From: Alex Shi <alex.shi@linux.alibaba.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
lizefan@huawei.com, Harry Wei <harryxiyou@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ben Hutchings <ben@decadent.org.uk>,
Tom Lendacky <thomas.lendacky@amd.com>,
Tony Luck <tony.luck@intel.com>,
Kees Cook <keescook@chromium.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] docs/zh_CN: add Chinese version of embargoed hardware issues
Date: Tue, 31 Dec 2019 14:23:52 +0800 [thread overview]
Message-ID: <52513678-9ec4-b472-edc2-9656d8a3c3fa@linux.alibaba.com> (raw)
In-Reply-To: <20191230120105.7776cbb4@lwn.net>
在 2019/12/31 上午3:01, Jonathan Corbet 写道:
> On Fri, 20 Dec 2019 11:04:43 +0800
> Alex Shi <alex.shi@linux.alibaba.com> wrote:
>
>> Embargoed hardware issues is a necessary process guide, but leak of
>> Chinese version, since there is more Chinese hardware vendors in market.
>> We'd better have a Chinese version of this guide.
>>
>> This patch translate the guide, add it into toctree. and also add a link
>> stub for the original doc.
>
> I've applied this (and the other two as well), thanks.
>
Thanks a lot! :)
Alex
prev parent reply other threads:[~2019-12-31 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 3:04 [PATCH v3 1/3] docs/zh_CN: add Chinese version of embargoed hardware issues Alex Shi
2019-12-20 3:04 ` [PATCH v3 2/3] docs/zh_CN: translate kernel driver statement into Chinese Alex Shi
2019-12-20 3:04 ` [PATCH v3 3/3] docs/zh_CN: translate kernel enforcement statement Alex Shi
2019-12-30 19:01 ` [PATCH v3 1/3] docs/zh_CN: add Chinese version of embargoed hardware issues Jonathan Corbet
2019-12-31 6:23 ` Alex Shi [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=52513678-9ec4-b472-edc2-9656d8a3c3fa@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=harryxiyou@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=sashal@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@intel.com \
/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).