From: Jonathan Corbet <corbet@lwn.net>
To: LIU Haoyang <tttturtleruss@gmail.com>,
Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: LIU Haoyang <tttturtleruss@gmail.com>,
cocci@inria.fr, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/dev-tools: fix a broken URL in dev-tools/coccinelle.rst
Date: Mon, 09 Mar 2026 10:10:18 -0600 [thread overview]
Message-ID: <87v7f5vv9x.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260308100851.341-1-tttturtleruss@gmail.com>
LIU Haoyang <tttturtleruss@gmail.com> writes:
> The original supplemental documentation for coccicheck is
> https://bottest.wiki.kernel.org/coccicheck, which redirects to a not found page,
> thus change it to https://bottest.wiki.kernel.org/coccicheck.html,
> which adds a suffix to original URL to make it direct to the right page.
>
> Signed-off-by: LIU Haoyang <tttturtleruss@gmail.com>
> ---
> Documentation/dev-tools/coccinelle.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/coccinelle.rst b/Documentation/dev-tools/coccinelle.rst
> index 2b942e3c8049..f73ccf5397f3 100644
> --- a/Documentation/dev-tools/coccinelle.rst
> +++ b/Documentation/dev-tools/coccinelle.rst
> @@ -61,7 +61,7 @@ Supplemental documentation
>
> For supplemental documentation refer to the wiki:
>
> -https://bottest.wiki.kernel.org/coccicheck
> +https://bottest.wiki.kernel.org/coccicheck.html
>
> The wiki documentation always refers to the linux-next version of the script.
I'll apply this - a working URL is better than a broken one. But is
there really nothing better to link to than a page that warns "OBSOLETE
CONTENT" at the top?
Thanks,
jon
next prev parent reply other threads:[~2026-03-09 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 10:08 [PATCH] docs/dev-tools: fix a broken URL in dev-tools/coccinelle.rst LIU Haoyang
2026-03-09 1:22 ` Dongliang Mu
2026-03-09 16:10 ` Jonathan Corbet [this message]
2026-03-09 16:28 ` Haoyang Liu
2026-03-10 0:10 ` Nicolas Palix
2026-03-10 7:39 ` Julia Lawall
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=87v7f5vv9x.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=skhan@linuxfoundation.org \
--cc=tttturtleruss@gmail.com \
--cc=workflows@vger.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