From: Julia Lawall <julia.lawall@inria.fr>
To: "相浦彰 / AIURA,AKIRA" <akira.aiura.bj@hitachi.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"Julia.Lawall@inria.fr" <Julia.Lawall@inria.fr>,
"maennich@google.com" <maennich@google.com>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"cocci@inria.fr" <cocci@inria.fr>,
"筒井勇介 / TSUTSUI,YUSUKE" <yusuke.tsutsui.gt@hitachi.com>,
"阿口誠司 / AGUCHI,SEIJI" <seiji.aguchi.tr@hitachi.com>,
"木村将希 / KIMURA,MASAKI" <masaki.kimura.kz@hitachi.com>,
"斉藤雅和 / SAITOU,MASAKAZU" <masakazu.saito.jn@hitachi.com>,
"山内大和 / YAMAUCHI,HIROKAZU" <hirokazu.yamauchi.hk@hitachi.com>
Subject: Re: [PATCH] coccinelle: update Coccinelle website URL
Date: Thu, 30 Jul 2026 07:55:58 +0200 (CEST) [thread overview]
Message-ID: <c511e35e-ded-839c-c2e9-6774e2e5ac0@inria.fr> (raw)
In-Reply-To: <TYTPR01MB1104567F06F7DA6B366C264A9D5C92@TYTPR01MB11045.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2745 bytes --]
On Thu, 30 Jul 2026, 相浦彰 / AIURA,AKIRA wrote:
>
> The old Coccinelle project URL is no longer available. Replace it with
> the current Coccinelle homepage already referenced by
> Documentation/dev-tools/coccinelle.rst.
>
> Signed-off-by: Akira Aiura <akira.aiura.bj@hitachi.com>
Applied. Thanks for the update.
julia
> ---
> Documentation/process/4.Coding.rst | 3 ++-
> scripts/coccicheck | 4 ++--
> scripts/nsdeps | 2 +-
> 3 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/process/4.Coding.rst b/Documentation/process/4.Coding.rst
> index c0f57d0c4f73..c23b9e48ce49 100644
> --- a/Documentation/process/4.Coding.rst
> +++ b/Documentation/process/4.Coding.rst
> @@ -312,7 +312,8 @@ be found at https://sparse.wiki.kernel.org/index.php/Main_Page if your
> distributor does not package it); it can then be run on the code by adding
> "C=1" to your make command.
>
> -The "Coccinelle" tool (http://coccinelle.lip6.fr/) is able to find a wide
> +The "Coccinelle" tool
> +(https://coccinelle.gitlabpages.inria.fr/website) is able to find a wide
> variety of potential coding problems; it can also propose fixes for those
> problems. Quite a few "semantic patches" for the kernel have been packaged
> under the scripts/coccinelle directory; running "make coccicheck" will run
> diff --git a/scripts/coccicheck b/scripts/coccicheck
> index 8dd766009de1..a0a0e0f72bc7 100755
> --- a/scripts/coccicheck
> +++ b/scripts/coccicheck
> @@ -11,7 +11,7 @@ DIR="$(dirname $(readlink -f $0))/.."
> SPATCH="`which ${SPATCH:=spatch}`"
>
> if [ ! -x "$SPATCH" ]; then
> - echo 'spatch is part of the Coccinelle project and is available at http://coccinelle.lip6.fr/'
> + echo 'spatch is part of the Coccinelle project and is available at https://coccinelle.gitlabpages.inria.fr/website'
> exit 1
> fi
>
> @@ -229,7 +229,7 @@ coccinelle () {
> echo " in $FILE."
> echo ''
> echo ' More information about semantic patching is available at'
> - echo ' http://coccinelle.lip6.fr/'
> + echo ' https://coccinelle.gitlabpages.inria.fr/website'
> echo ''
>
> if [ "`sed -ne 's|^//#||p' $COCCI`" ] ; then
> diff --git a/scripts/nsdeps b/scripts/nsdeps
> index a3372166ac01..d4b5ebcc2016 100644
> --- a/scripts/nsdeps
> +++ b/scripts/nsdeps
> @@ -8,7 +8,7 @@ SPATCH_REQ_VERSION="1.0.4"
> DIR="$(dirname $(readlink -f $0))/.."
> SPATCH="`which ${SPATCH:=spatch}`"
> if [ ! -x "$SPATCH" ]; then
> - echo 'spatch is part of the Coccinelle project and is available at http://coccinelle.lip6.fr/'
> + echo 'spatch is part of the Coccinelle project and is available at https://coccinelle.gitlabpages.inria.fr/website'
> exit 1
> fi
>
> --
> 2.53.0
>
>
prev parent reply other threads:[~2026-07-30 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 2:38 [PATCH] coccinelle: update Coccinelle website URL 相浦彰 / AIURA,AKIRA
2026-07-30 5:55 ` 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=c511e35e-ded-839c-c2e9-6774e2e5ac0@inria.fr \
--to=julia.lawall@inria.fr \
--cc=akira.aiura.bj@hitachi.com \
--cc=cocci@inria.fr \
--cc=corbet@lwn.net \
--cc=hirokazu.yamauchi.hk@hitachi.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maennich@google.com \
--cc=masakazu.saito.jn@hitachi.com \
--cc=masaki.kimura.kz@hitachi.com \
--cc=seiji.aguchi.tr@hitachi.com \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
--cc=yusuke.tsutsui.gt@hitachi.com \
/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