All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linux.alibaba.com>
To: Yanteng Si <siyanteng@loongson.cn>, Jonathan Corbet <corbet@lwn.net>
Cc: Harry Wei <harryxiyou@gmail.com>,
	Yanteng Si <siyanteng01@gmail.com>,
	linux-doc@vger.kernel.org, realpuyuwang@gmail.com,
	Huacai Chen <chenhuacai@gmail.com>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH v2 3/5] docs/zh_CN: add riscv patch-acceptance.rst translation
Date: Wed, 24 Feb 2021 11:41:59 +0800	[thread overview]
Message-ID: <4bbb0e30-9719-bd88-69fa-08a9ac768d19@linux.alibaba.com> (raw)
In-Reply-To: <20210224031149.15179-4-siyanteng@loongson.cn>

Reviewed-by: Alex Shi <alex.shi@linux.alibaba.com>

在 2021/2/24 上午11:11, Yanteng Si 写道:
> This patch translates Documentation/riscv/patch-acceptance.rst into Chineae.
> 
> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> ---
>  .../zh_CN/riscv/patch-acceptance.rst          | 32 +++++++++++++++++++
>  1 file changed, 32 insertions(+)
>  create mode 100644 Documentation/translations/zh_CN/riscv/patch-acceptance.rst
> 
> diff --git a/Documentation/translations/zh_CN/riscv/patch-acceptance.rst b/Documentation/translations/zh_CN/riscv/patch-acceptance.rst
> new file mode 100644
> index 000000000000..75446871559f
> --- /dev/null
> +++ b/Documentation/translations/zh_CN/riscv/patch-acceptance.rst
> @@ -0,0 +1,32 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +.. include:: ../disclaimer-zh_CN.rst
> +
> +:Original: :doc:`../../../riscv/patch-acceptance`
> +:Translator: Yanteng Si <siyanteng@loongson.cn>
> +
> +.. _cn_riscv_patch-acceptance:
> +
> +
> +arch/riscv 开发者维护指南
> +=========================
> +
> +概述
> +----
> +RISC-V指令集体系结构是公开开发的:
> +正在进行的草案可供所有人查看和测试实现。新模块或者扩展草案可能会在开发过程中发
> +生更改---有时以不兼容的方式对以前的草案进行更改。这种灵活性可能会给RISC-V Linux
> +维护者带来挑战。Linux开发过程更喜欢经过良好检查和测试的代码,而不是试验代码。我
> +们希望推广同样的规则到即将被内核合并的RISC-V相关代码。
> +
> +提交补遗清单
> +-------------------------
> +如果RISC-V基金会将这些模块或扩展的规范列为“冻结”或“已批准”,则我们仅接受新模块
> +或扩展的补丁。 (爱好者当然可以维护自己的Linux内核树,其中包含所需代码扩展草案
> +的代码。)
> +
> +此外,RISC-V规范允许爱好者创建自己的自定义扩展。这些自定义拓展不需要通过RISC-V
> +基金会的任何审核或批准。为了避免将爱好者一些特别的RISC-V拓展添加进内核代码带来
> +的维护复杂性和对性能的潜在影响,我们将只接受RISC-V基金会正式冻结或批准的的扩展
> +补丁。(爱好者当然可以维护自己的Linux内核树,其中包含他们想要的任何自定义扩展
> +的代码。)
> 

  reply	other threads:[~2021-02-24  3:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  3:11 [PATCH v2 0/5] docs/zh_CN:add riscv translation Yanteng Si
2021-02-24  3:11 ` [PATCH v2 1/5] docs/zh_CN:add riscv boot-image-header.rst translation Yanteng Si
2021-02-24  3:41   ` Alex Shi
2021-02-24  3:11 ` [PATCH v2 2/5] docs/zh_CN: add riscv features.rst translation Yanteng Si
2021-02-24  3:43   ` Alex Shi
2021-02-25  9:47     ` yanteng si
2021-02-24  3:11 ` [PATCH v2 3/5] docs/zh_CN: add riscv patch-acceptance.rst translation Yanteng Si
2021-02-24  3:41   ` Alex Shi [this message]
2021-02-24  3:11 ` [PATCH v2 4/5] docs/zh_CN: add riscv pmu.rst translation Yanteng Si
2021-02-24  3:43   ` Alex Shi
2021-02-24  3:11 ` [PATCH v2 5/5] docs/zh_CN: add riscv index.rst translation Yanteng Si
2021-02-24  3:43   ` Alex Shi

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=4bbb0e30-9719-bd88-69fa-08a9ac768d19@linux.alibaba.com \
    --to=alex.shi@linux.alibaba.com \
    --cc=chenhuacai@gmail.com \
    --cc=corbet@lwn.net \
    --cc=harryxiyou@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=realpuyuwang@gmail.com \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.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 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.