qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [PATCH for-10.2 3/8] scripts: Import Python kerneldoc from Linux kernel
Date: Fri, 15 Aug 2025 11:19:57 +0100	[thread overview]
Message-ID: <CAFEAcA_cWSGXQtAKdXZwZ+SPt_ipLKBn6d+4Z3ApAj1dnEYnPQ@mail.gmail.com> (raw)
In-Reply-To: <20250814171324.1614516-4-peter.maydell@linaro.org>

On Thu, 14 Aug 2025 at 18:13, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> We last synced our copy of kerneldoc with Linux back in 2020.  In the
> interim, upstream has entirely rewritten the script in Python, and
> the new Python version is split into a main script plus some
> libraries in the kernel's scripts/lib/kdoc.
>
> Import all these files.  These are the versions as of kernel commit
> 0cc53520e68be, with no local changes.
>
> We use the same lib/kdoc/ directory as the kernel does here, so we
> can avoid having to edit the top-level script just to adjust a
> pathname, even though it is probably not the naming we would have
> picked if this was a purely QEMU script.

>  scripts/kernel-doc.py           |  325 ++++++
>  scripts/lib/kdoc/kdoc_files.py  |  291 ++++++
>  scripts/lib/kdoc/kdoc_item.py   |   42 +
>  scripts/lib/kdoc/kdoc_output.py |  749 ++++++++++++++
>  scripts/lib/kdoc/kdoc_parser.py | 1669 +++++++++++++++++++++++++++++++
>  scripts/lib/kdoc/kdoc_re.py     |  270 +++++

We could alternatively put the whole thing into a subdir, e.g.:

   scripts/kdoc/kernel-doc.py
   scripts/kdoc/lib/kdoc/kdoc_files.py
   scripts/kdoc/lib/kdoc/kdoc_item.py
   etc

if we don't like having lib/ at the top level of our
scripts/ directory.  The thing the script cares about
is that the relative path from kernel-doc.py to the
lib/kdoc files is the same.

thanks
-- PMM


  parent reply	other threads:[~2025-08-15 10:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 17:13 [PATCH for-10.2 0/8] docs: Update our kernel-doc script to the kernel's new Python one Peter Maydell
2025-08-14 17:13 ` [PATCH for-10.2 1/8] docs/sphinx/kerneldoc.py: Handle new LINENO syntax Peter Maydell
2025-08-15  9:49   ` Mauro Carvalho Chehab
2025-08-14 17:13 ` [PATCH for-10.2 2/8] tests/qtest/libqtest.h: Remove stray space from doc comment Peter Maydell
2025-08-15  9:51   ` Mauro Carvalho Chehab
2025-08-15 10:14     ` Peter Maydell
2025-08-14 17:13 ` [PATCH for-10.2 3/8] scripts: Import Python kerneldoc from Linux kernel Peter Maydell
2025-08-15 10:00   ` Mauro Carvalho Chehab
2025-08-15 10:19   ` Peter Maydell [this message]
2025-08-14 17:13 ` [PATCH for-10.2 4/8] scripts/kernel-doc: strip QEMU_ from function definitions Peter Maydell
2025-08-15 10:01   ` Mauro Carvalho Chehab
2025-08-14 17:13 ` [PATCH for-10.2 5/8] scripts/kernel-doc: tweak for QEMU coding standards Peter Maydell
2025-08-15 10:34   ` Mauro Carvalho Chehab
2025-08-14 17:13 ` [PATCH for-10.2 6/8] scripts/kerneldoc: Switch to the Python kernel-doc script Peter Maydell
2025-08-14 17:13 ` [PATCH for-10.2 7/8] scripts/kernel-doc: Delete the old Perl " Peter Maydell
2025-08-15 10:35   ` Mauro Carvalho Chehab
2025-08-14 17:13 ` [PATCH for-10.2 8/8] MAINTAINERS: Put kernel-doc under the "docs build machinery" section Peter Maydell
2025-08-15 10:40   ` Mauro Carvalho Chehab
2025-08-26 10:36     ` Peter Maydell
2025-08-15  9:11 ` [PATCH for-10.2 0/8] docs: Update our kernel-doc script to the kernel's new Python one Jonathan Cameron via
2025-08-15  9:39   ` Mauro Carvalho Chehab
2025-08-15 10:10     ` Peter Maydell
2025-08-15 11:12       ` Mauro Carvalho Chehab
2025-08-19 10:34 ` Paolo Bonzini

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=CAFEAcA_cWSGXQtAKdXZwZ+SPt_ipLKBn6d+4Z3ApAj1dnEYnPQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).