From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH 6/6] ipe: update the project and test suite links
Date: Sat, 03 Oct 2026 02:55:51 +0000 [thread overview]
Message-ID: <20261003025551.9E4091F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261003025135.3666767-7-wufan@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] docs: missing test suite link update in zh_CN ipe.rst translation
--
commit 74b3b0aa8d1b1dfdacaa4326fe2dba8c20c146af
Author: Fan Wu <wufan@kernel.org>
ipe: update the project and test suite links
This commit updates the IPE project website and integration tests repository
links in the documentation. It points the developer documentation to the new
test suite repository.
[ ... ]
> diff --git a/Documentation/security/ipe.rst b/Documentation/security/ipe.rst
> index 5eb3e6265fbde..4490aed5918a6 100644
> --- a/Documentation/security/ipe.rst
> +++ b/Documentation/security/ipe.rst
> @@ -442,5 +442,5 @@ IPE has KUnit Tests for the policy parser. Recommended kunitconfig::
> CONFIG_SECURITY_IPE_KUNIT_TEST=y
>
> In addition, IPE has a python based integration
> -`test suite <https://github.com/microsoft/ipe/tree/test-suite>`_ that
> +`test suite <https://github.com/Integrity-Policy-Enforcement/ci>`_ that
[Severity: Low]
Is the translated Chinese documentation missing this update?
Looking at Documentation/translations/zh_CN/security/ipe.rst, it still
points to the old repository:
此外,IPE 具有一个基于 Python 的集成
`测试套件 <https://github.com/microsoft/ipe/tree/test-suite>`_
可以测试用户界面和强制执行功能。
Should this file also be updated to use the new Integrity-Policy-Enforcement/ci
link?
> can test both user interfaces and enforcement functionalities.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261003025135.3666767-1-wufan@kernel.org?part=6
next prev parent reply other threads:[~2026-10-03 2:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 2:51 [PATCH 0/6] ipe: cleanups, an audit fix and updated links Fan Wu
2026-10-03 2:51 ` [PATCH 1/6] ipe: constify token_default() Fan Wu
2026-10-03 2:56 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 2/6] ipe: use designated initializers for audit name tables Fan Wu
2026-10-03 2:59 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 3/6] ipe: check parser token table sizes Fan Wu
2026-10-03 2:56 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 4/6] ipe: correct policy text ownership comment Fan Wu
2026-10-03 2:57 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 5/6] ipe: fix enforcement audit Fan Wu
2026-10-03 2:55 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 6/6] ipe: update the project and test suite links Fan Wu
2026-10-03 2:55 ` sashiko-bot [this message]
2026-10-06 16:59 ` [PATCH 0/6] ipe: cleanups, an audit fix and updated links Fan Wu
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=20261003025551.9E4091F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.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