From: Yanteng Si <si.yanteng@linux.dev>
To: Shuo Zhao <zhaoshuo@cqsoftware.com.cn>, alexs@kernel.org, corbet@lwn.net
Cc: zhaoyuehui@cqsoftware.com.cn, zhangwei@cqsoftware.com.cn,
maoyuxian@cqsoftware.com.cn, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] docs/zh_CN: Add security lsm-development Chinese translation
Date: Fri, 21 Mar 2025 18:01:57 +0800 [thread overview]
Message-ID: <be3aa70b-a9c6-4a37-8b98-29c84177a3ff@linux.dev> (raw)
In-Reply-To: <1d7b8c13052f008def17b2ad923fc83bc53e32e1.1742542887.git.zhaoshuo@cqsoftware.com.cn>
在 3/21/25 3:49 PM, Shuo Zhao 写道:
> Translate .../security/lsm-development.rst into Chinese.
>
> Update the translation through commit 6d2ed653185b
> ("lsm: move hook comments docs to security/security.c")
>
> Signed-off-by: Shuo Zhao <zhaoshuo@cqsoftware.com.cn>
Where has my Reviewed-by tag gone?
Thanks,
Yanteng
> ---
> .../translations/zh_CN/security/index.rst | 2 +-
> .../zh_CN/security/lsm-development.rst | 19 +++++++++++++++++++
> 2 files changed, 20 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/translations/zh_CN/security/lsm-development.rst
>
> diff --git a/Documentation/translations/zh_CN/security/index.rst b/Documentation/translations/zh_CN/security/index.rst
> index 78d9d4b36dca..05d24e3acc11 100644
> --- a/Documentation/translations/zh_CN/security/index.rst
> +++ b/Documentation/translations/zh_CN/security/index.rst
> @@ -18,6 +18,7 @@
> credentials
> snp-tdx-threat-model
> lsm
> + lsm-development
> sak
> self-protection
> siphash
> @@ -28,7 +29,6 @@
> TODOLIST:
> * IMA-templates
> * keys/index
> -* lsm-development
> * SCTP
> * secrets/index
> * ipe
> diff --git a/Documentation/translations/zh_CN/security/lsm-development.rst b/Documentation/translations/zh_CN/security/lsm-development.rst
> new file mode 100644
> index 000000000000..cdd0aa03e089
> --- /dev/null
> +++ b/Documentation/translations/zh_CN/security/lsm-development.rst
> @@ -0,0 +1,19 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +.. include:: ../disclaimer-zh_CN.rst
> +
> +:Original: Documentation/security/lsm-development.rst
> +
> +:翻译:
> + 赵硕 Shuo Zhao <zhaoshuo@cqsoftware.com.cn>
> +
> +=================
> +Linux安全模块开发
> +=================
> +
> +基于 https://lore.kernel.org/r/20071026073721.618b4778@laptopd505.fenrus.org,
> +当一种新的LSM的意图(它试图防范什么,以及在哪些情况下人们会期望使用它)在
> +``Documentation/admin-guide/LSM/`` 中适当记录下来后,就会被接受进入内核。
> +这使得LSM的代码可以很轻松的与其目标进行对比,从而让最终用户和发行版可以更
> +明智地决定那些LSM适合他们的需求。
> +
> +有关可用的 LSM 钩子接口的详细文档,请参阅 ``security/security.c`` 及相关结构。
next prev parent reply other threads:[~2025-03-21 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 7:49 [PATCH 0/2] Add security lsm-development and SCTP Chinese translation Shuo Zhao
2025-03-21 7:49 ` [PATCH 2/2] docs/zh_CN: Add security " Shuo Zhao
2025-03-21 10:03 ` Yanteng Si
[not found] ` <1d7b8c13052f008def17b2ad923fc83bc53e32e1.1742542887.git.zhaoshuo@cqsoftware.com.cn>
2025-03-21 10:01 ` Yanteng Si [this message]
2025-03-22 13:08 ` [PATCH 1/2] docs/zh_CN: Add security lsm-development " 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=be3aa70b-a9c6-4a37-8b98-29c84177a3ff@linux.dev \
--to=si.yanteng@linux.dev \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=maoyuxian@cqsoftware.com.cn \
--cc=zhangwei@cqsoftware.com.cn \
--cc=zhaoshuo@cqsoftware.com.cn \
--cc=zhaoyuehui@cqsoftware.com.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;
as well as URLs for NNTP newsgroup(s).