From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] Docs: conf.py: fix typos in comments
Date: Fri, 26 Jun 2026 12:07:49 +0200 [thread overview]
Message-ID: <20260626120749.2f3dc318@localhost> (raw)
In-Reply-To: <20260626005248.1121464-1-rdunlap@infradead.org>
On Thu, 25 Jun 2026 17:52:48 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> Change "variabled" to "variables".
> Change "relative patch" to "relative path".
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
>
> Documentation/conf.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linext-2026-0623.orig/Documentation/conf.py
> +++ linext-2026-0623/Documentation/conf.py
> @@ -61,12 +61,12 @@ manpages_url = 'https://man7.org/linux/m
>
> def config_init(app, config):
> """
> - Initialize path-dependent variabled
> + Initialize path-dependent variables
>
> On Sphinx, all directories are relative to what it is passed as
> SOURCEDIR parameter for sphinx-build. Due to that, all patterns
> that have directory names on it need to be dynamically set, after
> - converting them to a relative patch.
> + converting them to a relative path.
>
> As Sphinx doesn't include any patterns outside SOURCEDIR, we should
> exclude relative patterns that start with "../".
--
Thanks,
Mauro
prev parent reply other threads:[~2026-06-26 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 0:52 [PATCH] Docs: conf.py: fix typos in comments Randy Dunlap
2026-06-26 10:07 ` Mauro Carvalho Chehab [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=20260626120749.2f3dc318@localhost \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox