public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Akira Yokosawa <akiyks@gmail.com>, Shuah Khan <shuah@kernel.org>,
	Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH 2/2] Move kernel-doc to tools/docs
Date: Mon, 19 Jan 2026 11:27:25 +0100	[thread overview]
Message-ID: <20260119112725.67b364f7@foz.lan> (raw)
In-Reply-To: <20260114164146.532916-3-corbet@lwn.net>

Em Wed, 14 Jan 2026 09:41:44 -0700
Jonathan Corbet <corbet@lwn.net> escreveu:

> kernel-doc is the last documentation-related tool still living outside of
> the tools/docs directory; the time has come to move it over.
> 
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>

...

> diff --git a/scripts/kernel-doc.py b/tools/docs/kernel-doc
> similarity index 100%
> rename from scripts/kernel-doc.py
> rename to tools/docs/kernel-doc

As reported by kernel test robot:
	 https://lore.kernel.org/linux-doc/202601191546.Bvd74asP-lkp@intel.com/

Here, you also need to change the relative location of the modules:

	 # Import Python modules

	-LIB_DIR = "../tools/lib/python"
	+LIB_DIR = "../lib/python"
	 SRC_DIR = os.path.dirname(os.path.realpath(__file__))

	 sys.path.insert(0, os.path.join(SRC_DIR, LIB_DIR))

Thanks,
Mauro

  parent reply	other threads:[~2026-01-19 10:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 16:41 [PATCH 0/2] Move kernel-doc to tools/docs Jonathan Corbet
2026-01-14 16:41 ` [PATCH 1/2] docs: kdoc: remove support for an external kernel-doc from sphinx Jonathan Corbet
2026-01-14 19:42   ` Mauro Carvalho Chehab
2026-01-14 16:41 ` [PATCH 2/2] Move kernel-doc to tools/docs Jonathan Corbet
2026-01-14 20:00   ` Mauro Carvalho Chehab
2026-01-19  8:23   ` kernel test robot
2026-01-19 10:27   ` Mauro Carvalho Chehab [this message]
2026-01-14 19:20 ` [PATCH 0/2] " Randy Dunlap
2026-01-14 19:24   ` Jonathan Corbet
2026-01-14 20:25     ` Mauro Carvalho Chehab
2026-01-15 10:33       ` Jani Nikula
2026-01-15 12:23         ` Mauro Carvalho Chehab
2026-01-15 12:58           ` Jani Nikula
2026-01-15 15:05         ` Jonathan Corbet
2026-01-15 17:31           ` Randy Dunlap
2026-01-15 18:04             ` Jonathan Corbet
2026-01-15 18:48               ` Randy Dunlap
2026-01-16 10:38               ` Jani Nikula
2026-01-16 17:44                 ` Jonathan Corbet
2026-01-17 10:29                   ` Mauro Carvalho Chehab
2026-01-16 17:48       ` Jonathan Corbet
2026-01-17 10:00         ` Mauro Carvalho Chehab
2026-01-17 18:09           ` Randy Dunlap
2026-01-19 10:17             ` 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=20260119112725.67b364f7@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=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=shuah@kernel.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