[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e84e288af0536cdc406c787301bc6b9b11c0be0a@intel.com>
Date: Thu, 14 Aug 2025 17:59:26 +0300
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Mauro Carvalho Chehab
<mchehab+huawei@...nel.org>, Akira Yokosawa <akiyks@...il.com>, Randy
Dunlap <rdunlap@...radead.org>, Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH RFC 00/13] Collect documention-related tools under
tools/doc
On Wed, 13 Aug 2025, Jonathan Corbet <corbet@....net> 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/doc, 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.
A wholehearted
Acked-by: Jani Nikula <jani.nikula@...el.com>
on all of 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.
lib/ contains code that's built into the kernel, I think lib/python
would be out of place.
IMO tools/python (or tools/lib/python, no strong opinion) is more
appropriate.
BR,
Jani.
--
Jani Nikula, Intel
Powered by blists - more mailing lists