From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH RFC 00/13] Collect documention-related tools under tools/doc
Date: Fri, 15 Aug 2025 11:29:13 +0300 [thread overview]
Message-ID: <5a17445f2ebb4a1290df1d046f0752f7fd8742d1@intel.com> (raw)
In-Reply-To: <b63fb30a-5d33-42bd-bdf3-b8dfb960bdf5@infradead.org>
On Thu, 14 Aug 2025, Randy Dunlap <rdunlap@infradead.org> wrote:
> Would tools/docs/lib be OK?
> I wouldn't tie it up to a specific language,
> but I don't have a strong opinion either way.
I think the question is, is the directory for libraries used by
documentation tools *or* for python libraries used by tools in general?
I would lean towards the latter, to not create another dilemma when a
library is used by both documentation and other tools.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-08-15 8:29 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 21:31 [PATCH RFC 00/13] Collect documention-related tools under tools/doc Jonathan Corbet
2025-08-13 21:32 ` [PATCH 01/13] docs: Move the "features" tools to tools/doc Jonathan Corbet
2025-08-13 23:38 ` Mauro Carvalho Chehab
2025-08-13 23:42 ` Randy Dunlap
2025-08-14 5:56 ` Mauro Carvalho Chehab
2025-08-14 5:57 ` Randy Dunlap
2025-08-13 21:32 ` [PATCH 02/13] docs: move checktransupdate.py " Jonathan Corbet
2025-08-13 23:51 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 03/13] docs: move scripts/check-variable-fonts.sh " Jonathan Corbet
2025-08-13 23:46 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 04/13] docs: move scripts/documentation-file-ref-check " Jonathan Corbet
2025-08-13 23:47 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 05/13] docs: move parallel-wrapper.sh to tools/doc/ Jonathan Corbet
2025-08-13 23:31 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 06/13] docs: move get_abi.py to tools/doc Jonathan Corbet
2025-08-13 23:43 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 07/13] docs: move sphinx-pre-install " Jonathan Corbet
2025-08-13 23:36 ` Mauro Carvalho Chehab
2025-08-14 2:14 ` Jonathan Corbet
2025-08-14 6:21 ` Mauro Carvalho Chehab
2025-08-14 13:52 ` Jonathan Corbet
2025-08-15 5:18 ` Mauro Carvalho Chehab
2025-08-15 13:18 ` Jonathan Corbet
2025-08-15 15:13 ` Mauro Carvalho Chehab
2025-08-15 19:31 ` Jonathan Corbet
2025-08-16 9:34 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 08/13] docs: move test_doc_build.py " Jonathan Corbet
2025-08-13 23:36 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 09/13] docs: move parse-headers.pl " Jonathan Corbet
2025-08-13 23:32 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 10/13] docs: move kernel-doc " Jonathan Corbet
2025-08-13 23:33 ` Mauro Carvalho Chehab
2025-08-13 23:48 ` Mauro Carvalho Chehab
2025-08-14 12:13 ` kernel test robot
2025-08-13 21:32 ` [PATCH 11/13] docs: move split-man.pl " Jonathan Corbet
2025-08-13 23:50 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 12/13] docs: move find-unused-docs.sh " Jonathan Corbet
2025-08-13 23:50 ` Mauro Carvalho Chehab
2025-08-13 21:32 ` [PATCH 13/13] docs: remove kernel-doc.pl Jonathan Corbet
2025-08-13 23:33 ` Mauro Carvalho Chehab
2025-08-15 2:43 ` Randy Dunlap
2025-08-15 4:45 ` Mauro Carvalho Chehab
2025-08-13 21:38 ` [PATCH RFC 00/13] Collect documention-related tools under tools/doc Jonathan Corbet
2025-08-13 23:29 ` Mauro Carvalho Chehab
2025-08-14 14:59 ` Jani Nikula
2025-08-15 2:53 ` Randy Dunlap
2025-08-15 8:29 ` Jani Nikula [this message]
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=5a17445f2ebb4a1290df1d046f0752f7fd8742d1@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--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 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.