From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Igor Mammedov <imammedo@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
John Snow <jsnow@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Shiju Jose <shiju.jose@huawei.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: [PATCH 0/1] Sync kernel-doc.py with Linux upstream
Date: Tue, 6 Jan 2026 17:38:18 +0100 [thread overview]
Message-ID: <cover.1767716928.git.mchehab+huawei@kernel.org> (raw)
Hi Peter/John,
There were several updates at kernel-doc upstream fixing bugs,
doing cleanups and a couple of improvements.
Better to keep QEMU in sync with such changes.
Worth mentioning that we did some changes on Linux at the
kernel-doc.py script itself, to avoid Kernel build to crash
with too old Python versions, as there docs build is a
separate target, and python >= 3.6 is a new requirement
there.
On kernel, if python < 3.6, it will simply ignore docs
build (emitting a warning).
I opted to not backport such changes, but if you prefer
doing that, I can do that on a v2.
---
For now, I opted to keep kernel-doc libraries at the same
directory as before - e.g. at scripts/lib/kdoc. On Linux,
we ended moving it to tools/lib/python/kdoc. It could make
sense to move it on QEMU too, as it makes a little bit
easier to keep things in sync.
What do you think?
Mauro Carvalho Chehab (1):
kernel-doc.py: sync with upstream Kernel v6.19-rc4
scripts/lib/kdoc/kdoc_files.py | 11 +-
scripts/lib/kdoc/kdoc_item.py | 3 +-
scripts/lib/kdoc/kdoc_output.py | 93 +++-
scripts/lib/kdoc/kdoc_parser.py | 897 ++++++++++++++++----------------
scripts/lib/kdoc/kdoc_re.py | 24 +-
5 files changed, 554 insertions(+), 474 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-06 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 16:38 Mauro Carvalho Chehab [this message]
2026-01-06 16:38 ` [PATCH 1/1] kernel-doc.py: sync with upstream Kernel v6.19-rc4 Mauro Carvalho Chehab
2026-01-20 12:55 ` Michael S. Tsirkin
2026-01-06 16:51 ` [PATCH 0/1] Sync kernel-doc.py with Linux upstream Daniel P. Berrangé
2026-01-13 11:44 ` Peter Maydell
2026-01-13 12:08 ` Daniel P. Berrangé
2026-01-13 13:04 ` Peter Maydell
2026-01-13 13:20 ` Daniel P. Berrangé
2026-01-13 19:52 ` John Snow
2026-01-13 20:04 ` Mauro Carvalho Chehab
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.1767716928.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=imammedo@redhat.com \
--cc=jsnow@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shiju.jose@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.