mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: 闲逛 <2368492046@qq.com>
To: "Weijie Yuan" <wy@wyuan.org>
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: [PATCH v2 0/4] docs: kernel-doc: fix export selection and error handling
Date: Sat, 14 Nov 2026 17:05:38 +0800	[thread overview]
Message-ID: <tencent_79B4A967C5ADFFCE3CCF0EA9362419ABE105@qq.com> (raw)
In-Reply-To: <avgDq_FrLSbuC7bK@wyuan.org>

Hi Weijie,

Thank you for reviewing my submission, and sorry for the mistakes.
Although I have been familiar with and using Linux for nearly ten
years, this is my first time submitting a bug fix to the kernel
community, and I still have a lot to learn about the process.

This v2 series fixes four kernel-doc issues:

  1. Pass the required transforms when parsing separate export files.
  2. Combine input and additional export sources correctly.
  3. Honor environment warning-as-error settings in the exit status.
  4. Import sys for YAML failure diagnostics.

I stopped after the regression tests, which was insufficient
validation. I should have completed the documentation build before
sending v1.

Full documentation builds have now completed on both the unmodified
docs-next base and the revised series, using Ubuntu 24.04 under WSL2
with Python 3.12.3 and Sphinx 7.2.6:

  make -j4 O=../baseline-lf-build htmldocs SPHINXOPTS='-j4'
  make -j4 O=../patched-build htmldocs SPHINXOPTS='-j4'

Both commands returned exit status 0 and generated 4,138 HTML pages.
Both logs contain the same 92 diagnostic lines after normalizing
source and output paths; the revised series adds no new diagnostics.

The failure was specific to my HTTPS attempt. Fetching through
git://git.lwn.net/linux.git, as listed in MAINTAINERS, worked.
My earlier explanation was incomplete.

The revised series is now based on docs-next commit:
2138148bf44fd84d3e0a863f0e8cb3627cdcc606

The follow-up review also identified missing coverage for combining
input and additional export files, and for relative SRCTREE paths.
These cases are now fixed and covered by regression tests. The full
suite on the revised docs-next tree runs 137 tests: 133 pass, with
four pre-existing expected failures.

I have also read the submission instructions you linked. I will send
v2 as separate inline plain-text patch emails, without attachments.

Thank you for your time and guidance.

Best regards,
yuehua-meng

  reply	other threads:[~2026-11-14  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14  5:40 [PATCH " 闲逛
2026-11-14  6:46 ` Weijie Yuan
2026-11-14  9:05   ` 闲逛 [this message]
2026-11-14 14:21     ` [PATCH v2 " 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_79B4A967C5ADFFCE3CCF0EA9362419ABE105@qq.com \
    --to=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 \
    --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

all inboxes | Powered by JetHome®