From: Randy Dunlap <rdunlap@infradead.org>
To: linux-doc@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: [PATCH] doc tools: fix 'path' typos
Date: Wed, 5 Aug 2026 22:56:34 -0700 [thread overview]
Message-ID: <20260806055634.1293294-1-rdunlap@infradead.org> (raw)
Correct "patch" or "patches" to "path" or "paths" in comments.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
tools/docs/documentation-file-ref-check | 2 +-
tools/docs/sphinx-build-wrapper | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
--- linux-next-20260805.orig/tools/docs/documentation-file-ref-check
+++ linux-next-20260805/tools/docs/documentation-file-ref-check
@@ -143,7 +143,7 @@ while (<IN>) {
# Check if exists, evaluating wildcards
next if (grep -e, glob("$ref $fulref"));
- # Accept relative Documentation patches for tools/
+ # Accept relative Documentation paths for tools/
if ($f =~ m/tools/) {
my $path = $f;
$path =~ s,(.*)/.*,$1,;
--- linux-next-20260805.orig/tools/docs/sphinx-build-wrapper
+++ linux-next-20260805/tools/docs/sphinx-build-wrapper
@@ -99,9 +99,9 @@ class SphinxBuilder:
def get_path(self, path, use_cwd=False, abs_path=False):
"""
- Ancillary routine to handle patches the right way, as shell does.
+ Ancillary routine to handle paths the right way, as shell does.
- It first expands "~" and "~user". Then, if patch is not absolute,
+ It first expands "~" and "~user". Then, if path is not absolute,
join self.srctree. Finally, if requested, convert to abspath.
"""
next reply other threads:[~2026-08-06 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 5:56 Randy Dunlap [this message]
2026-08-11 16:43 ` [PATCH] doc tools: fix 'path' typos Jonathan Corbet
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=20260806055634.1293294-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.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 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.