From: Alex Shi <seakeel@gmail.com>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>,
Dongliang Mu <dzm91@hust.edu.cn>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <kees@kernel.org>,
linux-doc@vger.kernel.org
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2] docs/zh_CN: fix CONFIG_CONPAT typo for CONFIG_COMPAT
Date: Mon, 6 Jul 2026 11:51:55 +0800 [thread overview]
Message-ID: <d199d200-37bc-437b-94c4-d23b4d1bbe17@gmail.com> (raw)
In-Reply-To: <20260613183737.11434-1-enelsonmoore@gmail.com>
Applied, Thanks!
On 2026/6/14 02:37, Ethan Nelson-Moore wrote:
> The Simplified Chinese translation of security/self-protection.rst
> contains a typo CONFIG_CONPAT for CONFIG_COMPAT. Fix it.
>
> Signed-off-by: Ethan Nelson-Moore<enelsonmoore@gmail.com>
> ---
> Changes in v2: remove unnecessary information from commit message
>
> Documentation/translations/zh_CN/security/self-protection.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/security/self-protection.rst b/Documentation/translations/zh_CN/security/self-protection.rst
> index 93de9cee5c1a..ad96bb4a4995 100644
> --- a/Documentation/translations/zh_CN/security/self-protection.rst
> +++ b/Documentation/translations/zh_CN/security/self-protection.rst
> @@ -97,7 +97,7 @@ ARCH_OPTIONAL_KERNEL_RWX时的默认设置。
> --------------------
>
> 对于64位系统，一种消除许多系统调用最简单的方法是构建时不启用
> -CONFIG_CONPAT。然而，这种情况通常不可行。
> +CONFIG_COMPAT。然而，这种情况通常不可行。
>
> “seccomp”系统为用户空间提供了一种可选功能，提供了一种减少可供
> 运行中进程使用内核入口点数量的方法。这限制了可以访问内核代码
> -- 2.43.0
>
prev parent reply other threads:[~2026-07-06 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-13 18:37 [PATCH v2] docs/zh_CN: fix CONFIG_CONPAT typo for CONFIG_COMPAT Ethan Nelson-Moore
2026-06-14 0:33 ` Zenghui Yu
2026-06-14 2:08 ` Dongliang Mu
2026-07-06 3:51 ` 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=d199d200-37bc-437b-94c4-d23b4d1bbe17@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=enelsonmoore@gmail.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
/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