From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 00/10] Collect documentation-related tools under /tools/docs
Date: Fri, 24 Oct 2025 12:10:54 +0900 [thread overview]
Message-ID: <532dcafa-08a8-4e18-b904-53e061734b69@gmail.com> (raw)
In-Reply-To: <20251023161027.697135-1-corbet@lwn.net>
Hi Jon,
On Thu, 23 Oct 2025 10:10:08 -0600, Jonathan Corbet wrote:
> Our documentation-related tools are spread out over various directories;
> several are buried in the scripts/ dumping ground. That makes them harder
> to discover and harder to maintain.
>
> Recently, the idea of creating a dedicated directory for documentation tools
> came up; I decided to see what it would look like. This series creates a
> new directory, tools/docs, and moves various utilities there, hopefully
> fixing up all of the relevant references in the process.
>
> At the end, rather than move the old, Perl kernel-doc, I simply removed it.
>
> The big elephant lurking in this small room is the home for Python modules;
> I left them under scripts/lib, but that is an even less appropriate place
> than it was before. I would propose either tools/python or lib/python;
> thoughts on that matter welcome.
>
> Changes in v2:
> - Rebase on top of all of Mauro's changes (the most painful rebase I've
> ever done, I think).
I tried to apply this series on top of current docs-next, and several earlier
merge points, but haven't succeeded so far, even with "git am -3" ...
Where am I supposed to apply this?
Thanks, Akira
> - Land everything in /tools/docs/ rather than /tools/doc/
>
> v1: https://lore.kernel.org/lkml/20250813213218.198582-1-corbet@lwn.net/
[...]
next prev parent reply other threads:[~2025-10-24 3:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 16:10 Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 01/10] docs: Move the "features" tools to tools/docs Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 02/10] docs: move checktransupdate.py " Jonathan Corbet
2025-10-25 10:29 ` Dongliang Mu
2025-10-23 16:10 ` [PATCH v2 03/10] docs: move scripts/check-variable-fonts.sh " Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 04/10] docs: move scripts/documentation-file-ref-check " Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 05/10] docs: move get_abi.py " Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 06/10] docs: move test_doc_build.py " Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 07/10] docs: move kernel-doc " Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 08/10] docs: move split-man.pl " Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 09/10] docs: move find-unused-docs.sh " Jonathan Corbet
2025-10-23 16:10 ` [PATCH v2 10/10] docs: remove kernel-doc.pl Jonathan Corbet
2025-10-24 3:10 ` Akira Yokosawa [this message]
2025-10-24 13:55 ` [PATCH v2 00/10] Collect documentation-related tools under /tools/docs Akira Yokosawa
2025-10-24 13:59 ` Jonathan Corbet
2025-10-24 13:05 ` Jani Nikula
2025-10-24 14:24 ` Mauro Carvalho Chehab
2025-10-24 15:37 ` Jonathan Corbet
2025-10-24 16:35 ` 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=532dcafa-08a8-4e18-b904-53e061734b69@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®