All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	John Snow <jsnow@redhat.com>
Subject: Re: [PATCH for-10.2 8/8] MAINTAINERS: Put kernel-doc under the "docs build machinery" section
Date: Fri, 15 Aug 2025 12:40:05 +0200	[thread overview]
Message-ID: <20250815124005.6a93d35b@foz.lan> (raw)
In-Reply-To: <20250814171324.1614516-9-peter.maydell@linaro.org>

Em Thu, 14 Aug 2025 18:13:23 +0100
Peter Maydell <peter.maydell@linaro.org> escreveu:

> We never had a MAINTAINERS entry for the old kernel-doc script; add
> the files for the new Python kernel-doc under "Sphinx documentation
> configuration and build machinery", as the most appropriate
> subsection.
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
>  MAINTAINERS | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a07086ed762..efa59ce7c36 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4436,6 +4436,8 @@ F: docs/sphinx/
>  F: docs/_templates/
>  F: docs/devel/docs.rst
>  F: docs/devel/qapi-domain.rst
> +F: scripts/kernel-doc
> +F: scripts/lib/kdoc/

If you want, feel free to add me there either as maintainer or
reviewer. I can gladly help you maintaining it.

Either way:

Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>

-

PS.: On a side note, there is a RFC still under discussion about
moving the script location upstream to tools/docs. Nothing decided
yet. One of the points we're still unsure is where we would place
the library directory. So, this may end being slipping to the next
kernel cycle.


>  
>  Rust build system integration
>  M: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>



Thanks,
Mauro


  reply	other threads:[~2025-08-15 10:40 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
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 [this message]
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=20250815124005.6a93d35b@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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.