public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
	"Petr Vorel" <pvorel@suse.cz>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH 00/25] Add tools/lib/python modules to Documentation/tools
Date: Fri, 23 Jan 2026 11:47:30 -0700	[thread overview]
Message-ID: <87h5sc17zx.fsf@trenco.lwn.net> (raw)
In-Reply-To: <cover.1768838938.git.mchehab+huawei@kernel.org>

Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:

> Hi Jon,
>
> This is an extended version of:
>     https://lore.kernel.org/linux-doc/cover.1768488832.git.mchehab+huawei@kernel.org/
>
> It basically adds everything we currently have inside libs/tool/python
> to "tools" book inside documentation.

OK, I have applied the set, thanks.

jon

  parent reply	other threads:[~2026-01-23 18:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 16:23 [PATCH 00/25] Add tools/lib/python modules to Documentation/tools Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 01/25] docs: custom.css: prevent li marker to override text Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 02/25] docs: conf.py: don't use doctree with a different meaning Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 03/25] docs: conf: don't rely on cwd to get documentation location Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 04/25] docs: enable Sphinx autodoc extension to allow documenting python Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 05/25] docs: custom.css: add CSS for python Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 06/25] docs: kdoc: latex_fonts: Improve docstrings and comments Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 07/25] docs: kdoc_files: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 08/25] docs: kdoc_item: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 09/25] docs: kdoc_parser: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 10/25] docs: kdoc_output: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 11/25] docs: kdoc_re: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 12/25] docs: kdoc: parse_data_structs: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 13/25] docs: kdoc: enrich_formatter: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 14/25] docs: kdoc: python_version: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 15/25] docs: add kernel-doc modules documentation Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 16/25] docs: add kabi " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 17/25] docs: python: abi_parser: do some improvements at documentation Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 18/25] docs: python: abi_regex: " Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 19/25] docs: kabi: system_symbols: end docstring phrases with a dot Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 20/25] docs: kabi: helpers: add helper for debug bits 7 and 8 Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 21/25] docs: kabi: helpers: add documentation for each "enum" value Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 22/25] docs: add jobserver module documentation Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 23/25] docs: jobserver: do some documentation improvements Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 24/25] docs: add parse_features module documentation Mauro Carvalho Chehab
2026-01-19 16:23 ` [PATCH 25/25] docs: parse_features: make documentation more consistent Mauro Carvalho Chehab
2026-01-23 18:47 ` Jonathan Corbet [this message]
2026-01-24  0:31   ` [PATCH 00/25] Add tools/lib/python modules to Documentation/tools Akira Yokosawa
2026-01-24  5:54     ` 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=87h5sc17zx.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nfraprado@collabora.com \
    --cc=pvorel@suse.cz \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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