From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>,
workflows@vger.kernel.org
Subject: [PATCH v2 0/2] Better handle and document Python needs for Kernel build
Date: Tue, 29 Jul 2025 18:43:02 +0200 [thread overview]
Message-ID: <cover.1753806485.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
It follows the second version of this small series. It contains
missing patches from the python backward-compatibility series.
I dropped support for 2.7 and did some changes at changes.rst
per Akira's request.
They're not urgent, IMO it should be OK to have them merged for 6.17.
The first patch ensures that kernel-doc won't crash with version
3.2 (tested on 3.4, as 3.2 is like an unicorn: docker containers v1
don't run anymore on Fedora, building is broken since at least
Fedora 32, Anaconda doesn't have it anymore).
With this change, on elder versions, it would emit a warning and
do nothing, as the actual code depends on features at 3.6 (f-strings)
and 3.7 (ordered dict).
The second patch changes process/changes.rst. Currently, it makes
one think that Python is optional. While not having python may
work on some cases, it breaks on arm/arm64 with defconfigs.
It also breaks with allyesconfig/almodconfig (at least on x86/x86_64),
with clang (on some archs) and apparently on some other
subsystems that I didn't care enough to identify, as for me,
breaking on arm/arm64 with defconfigs, and on x86/x86_64
with allyesconfig/allmodconfig is enough evidence that this
is mandatory nowadays.
So, remove optional from Python and add a quick description
about where it is required, leaving it open to one's imagination
that it could break with other configs we didn't map.
---
v2: drop support for 2.7, updated a comment and updated changes.rst.
Mauro Carvalho Chehab (2):
docs: kernel-doc: avoid script crash on ancient Python
docs: changes: better document Python needs
Documentation/process/changes.rst | 9 +++++++-
scripts/kernel-doc.py | 34 ++++++++++++++++++++++---------
2 files changed, 32 insertions(+), 11 deletions(-)
--
2.49.0
next reply other threads:[~2025-07-29 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 16:43 Mauro Carvalho Chehab [this message]
2025-07-29 16:43 ` [PATCH v2 2/2] docs: changes: better document Python needs Mauro Carvalho Chehab
2025-07-31 3:14 ` Akira Yokosawa
2025-08-04 18:08 ` Rob Herring
2025-08-11 16:58 ` [PATCH v2 0/2] Better handle and document Python needs for Kernel build Jonathan Corbet
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=cover.1753806485.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).