From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Dongliang Mu <dzm91@hust.edu.cn>, <si.yanteng@linux.dev>,
Alex Shi <alexs@kernel.org>, 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>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<llvm@lists.linux.dev>
Subject: Re: [PATCH] docs/zh_CN: fix one sentence in llvm.rst
Date: Thu, 7 Nov 2024 09:38:41 +0800 [thread overview]
Message-ID: <214a5a61-0ae6-09c8-9fce-c43b09a07f03@huawei.com> (raw)
In-Reply-To: <20241107013615.374757-1-dzm91@hust.edu.cn>
On 2024/11/7 9:35, Dongliang Mu wrote:
> According to Jinjie Ruan, the description about the prebuilt llvm is
> incorrect. Fix this sentence with new understanding.
>
> Link: https://groups.google.com/g/hust-os-kernel-patches/c/GbN5RkVrBho/m/2sC9rAw7BQAJ
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> ---
> Documentation/translations/zh_CN/kbuild/llvm.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/kbuild/llvm.rst b/Documentation/translations/zh_CN/kbuild/llvm.rst
> index f71092144a26..f87e0181d8e7 100644
> --- a/Documentation/translations/zh_CN/kbuild/llvm.rst
> +++ b/Documentation/translations/zh_CN/kbuild/llvm.rst
> @@ -188,7 +188,7 @@ LLVM 并不支持 Linux 内核所有可支持的架构，同样，即使 LLVM
>
> 我们在 `kernel.org <https://kernel.org/pub/tools/llvm/>`_ 提供预编译的稳定版 LLVM。
> 这些版本已经针对 Linux 内核构建，使用配置文件数据进行优化。相较于其他发行版中的 LLVM，它们应该
> -能提高内核构建时间。
> +能提高内核构建效率。
Reviewed-by: Jinjie Ruan <ruanjinjie@huawei.com>
>
> 以下是一些有助于从源代码构建 LLVM 或通过发行版的包管理器获取 LLVM 的链接。
>
next prev parent reply other threads:[~2024-11-07 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 1:35 Dongliang Mu
2024-11-07 1:38 ` Jinjie Ruan [this message]
2024-11-12 20:12 ` Jonathan Corbet
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=214a5a61-0ae6-09c8-9fce-c43b09a07f03@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--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=si.yanteng@linux.dev \
/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
all inboxes | Powered by JetHome®