workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Nicolas Palix <nicolas.palix@imag.fr>
Cc: Haoyang Liu <tttturtleruss@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	 Shuah Khan <skhan@linuxfoundation.org>,
	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: Tue, 10 Mar 2026 08:39:12 +0100 (CET)	[thread overview]
Message-ID: <4c157be7-7673-c513-65f0-f0222cf8d117@inria.fr> (raw)
In-Reply-To: <1c546ad7-14f8-4695-9754-32a020f8a082@imag.fr>

[-- Attachment #1: Type: text/plain, Size: 2178 bytes --]



On Tue, 10 Mar 2026, Nicolas Palix wrote:

> Hi,
>
> Maybe we can just throw away that section of "Supplemental documentation" and
> its link ?
>
> Nowadays, there is much more SmPL provided, and the rst file
> describes better and up-to-date information.
>
> Would a link to
> https://www.kernel.org/doc/html/latest/dev-tools/coccinelle.html
> be useful to point to latest version ?

OK, thanks.

There is also an out of date URL in that page.  I will send a patch.

julia

>
> Sincerely,
>
> Le 09/03/2026 à 17:28, Haoyang Liu a écrit :
> >
> > On 3/10/2026 12:10 AM, Jonathan Corbet wrote:
> > > 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?
> >
> > Dear Jon,
> >
> > Unfortunately, I do not find any other documents about this script, so I
> > have to use it even though it's obsolete.
> >
> > Sincerely,
> > Haoyang
> >
> > >
> > > Thanks,
> > >
> > > jon
> >
> >
> >
> >
>
>

      reply	other threads:[~2026-03-10  7:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08 10:08 LIU Haoyang
2026-03-09  1:22 ` Dongliang Mu
2026-03-09 16:10 ` Jonathan Corbet
2026-03-09 16:28   ` Haoyang Liu
2026-03-10  0:10     ` Nicolas Palix
2026-03-10  7:39       ` Julia Lawall [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=4c157be7-7673-c513-65f0-f0222cf8d117@inria.fr \
    --to=julia.lawall@inria.fr \
    --cc=cocci@inria.fr \
    --cc=corbet@lwn.net \
    --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