Linux Security Modules development
 help / color / mirror / Atom feed
From: Yan Zhu <zhuyan2015@qq.com>
To: Weijie Yuan <wy@wyuan.org>
Cc: dzm91@hust.edu.cn, skhan@linuxfoundation.org, gnoack@google.com,
	linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org,
	alexs@kernel.org, si.yanteng@linux.dev, corbet@lwn.net,
	mic@digikod.net
Subject: Re: [PATCH 00/10] docs/zh_CN: add LSM admin-guide Chinese translation
Date: Sun, 15 Nov 2026 22:03:43 +0800	[thread overview]
Message-ID: <tencent_EAF72EE1486DCC13E1E47DCFA5CF52290B05@qq.com> (raw)
In-Reply-To: <aunHXtl-L__1isgc@wyuan.org>

On 11/3/2026 7:37 PM, Weijie Yuan wrote:
> Yan Zhu <zhuyan2015@qq.com> writes:
> 
>> Ping
>>
>> On 6/12/2026 11:58 PM, Yan Zhu wrote:
>>> This patch series adds the Chinese translation for the Linux Security Module
>>> (LSM) admin-guide documentation, including the main index and all ten
>>> sub-pages: apparmor, LoadPin, SELinux, Smack, tomoyo, Yama, SafeSetID,
>>> ipe, and landlock.  The admin-guide toctree is also updated to list the
>>> newly translated LSM/index.
>>>
>>> The original English documentation was restructured into reStructuredText
>>> by Kees Cook in commit 504f231cda56 ("doc: ReSTify and split LSM.txt"),
>>> and each sub-page has been kept up-to-date with subsequent mainline changes.
>>>
>>>
>>> base: https://git.kernel.org/pub/scm/linux/kernel/git/alexs/linux.git docs-next
>>>
>>>
>>>
>>> Yan Zhu (10):
>>>     docs/zh_CN: add LSM/index Chinese translation
>>>     docs/zh_CN: add LSM/apparmor Chinese translation
>>>     docs/zh_CN: add LSM/LoadPin Chinese translation
>>>     docs/zh_CN: add LSM/SELinux Chinese translation
>>>     docs/zh_CN: add LSM/Smack Chinese translation
>>>     docs/zh_CN: add LSM/tomoyo Chinese translation
>>>     docs/zh_CN: add LSM/Yama Chinese translation
>>>     docs/zh_CN: add LSM/SafeSetID Chinese translation
>>>     docs/zh_CN: add LSM/ipe Chinese translation
>>>     docs/zh_CN: add LSM/landlock Chinese translation
> 
> Hi,
> 
> I suspect that your series was long since buried in maintainers' inbox,
> because your actual patches are not "In-Reply-To" this cover letter.
> 
> And I do remember I mentioned it elsewhere that it may has something to
> do with your QQ email server.  I suggest resending this serie after
> fixing email stuffs.

Thanks for your suggestion. I will resend these patches.

-- 
Thanks
Yan Zhu


  reply	other threads:[~2026-11-15 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 15:58 [PATCH 00/10] docs/zh_CN: add LSM admin-guide Chinese translation Yan Zhu
2026-10-24 15:07 ` Yan Zhu
2026-11-03 11:37   ` Weijie Yuan
2026-11-15 14:03     ` Yan Zhu [this message]
2026-11-04  2:25   ` Dongliang Mu
  -- strict thread matches above, loose matches on Subject: below --
2026-11-15 15:19 Yan Zhu
2026-11-16  0:45 ` Weijie Yuan
2026-11-16  1:26   ` Weijie Yuan

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=tencent_EAF72EE1486DCC13E1E47DCFA5CF52290B05@qq.com \
    --to=zhuyan2015@qq.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=gnoack@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=wy@wyuan.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