From: Weijie Yuan <wy@wyuan.org>
To: 闲逛 <2368492046@qq.com>
Cc: corbet <corbet@lwn.net>, mchehab <mchehab@kernel.org>,
linux-doc <linux-doc@vger.kernel.org>,
skhan <skhan@linuxfoundation.org>,
rdunlap <rdunlap@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] docs: kernel-doc: fix export selection and error handling
Date: Sat, 14 Nov 2026 14:46:03 +0800 [thread overview]
Message-ID: <avgDq_FrLSbuC7bK@wyuan.org> (raw)
In-Reply-To: <tencent_9BF64A4FFFB7B990DD5E6D6CF26C43565306@qq.com>
On Sat, Nov 14, 2026 at 01:40:28PM +0800, 闲逛 wrote:
> Hi Jonathan and Mauro,
>
> This series fixes four reproducible kernel-doc issues:
>
> 1. Multi-file export filtering reuses the first input's exports.
> 2. Environment warning-as-error settings do not affect the exit status.
> 3. YAML error paths call sys.exit() without importing sys.
> 4. A separate -export-file triggers a missing-xforms TypeError.
>
> Each fix includes CLI regression coverage. The warning-policy tests also
> cover KDOC_WERROR=0, empty overrides, and command-line precedence.
>
> Validation on Windows (Python 3.12) and Ubuntu 24.04 under WSL2
> (Python 3.12.3):
>
> python3 -B -X utf8 -m unittest discover -s tools/unittests
>
> Ran 131 tests: 127 passed, 4 existing expected failures.
>
> The series is based on mainline commit
> b3dfbde62cf1981c4638939c159dfd087b7a72e9.
> A complete Sphinx documentation build has not been performed.
May I ask why? You could just run 'make htmldocs'.
> I could not verify docs-next because the server's TLS connection
> failed; checking for equivalent pending mailing-list patches is also
> incomplete.
I don't believe you can not clone Jon's repo and checkout docs-next
branch. Is there any reason? (Looks like git.lwn.net is doing a pretty
good job of keeping AI crawlers out.;)) And I suspect that this part is
the output of your agent. :)
> Codex assisted with reproducing the failures, preparing the fixes and
> regression tests, and executing the tests. The task was to inspect and
> repair kernel-doc behavior in a local Linux source tree. I have reviewed
> the changes and requested that my Signed-off-by be recorded.
Thanks for the disclosure, but this may not be put in the commit message
of your patches. They should better be under '---'.
And please see also: "no attachments"
https://docs.kernel.org/process/submitting-patches.html#no-mime-no-links-no-compression-no-attachments-just-plain-text
Thanks.
prev parent reply other threads:[~2026-11-14 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 5:40 [PATCH 0/4] docs: kernel-doc: fix export selection and error handling 闲逛
2026-11-14 6:46 ` Weijie Yuan [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=avgDq_FrLSbuC7bK@wyuan.org \
--to=wy@wyuan.org \
--cc=2368492046@qq.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.org \
--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