[PATCH] coccinelle: update Coccinelle URL

[PATCH] coccinelle: update Coccinelle URL

[Julia Lawall]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 4842 bytes --]

The LIP6 URL no longer functions.

Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>

---

I used the UTF-8 encoding for the email.
Let me know if this was not the right choice.

 Documentation/dev-tools/coccinelle.rst                |    2 +-
 Documentation/translations/it_IT/process/4.Coding.rst |    3 ++-
 Documentation/translations/sp_SP/process/4.Coding.rst |    3 ++-
 Documentation/translations/zh_CN/process/4.Coding.rst |    2 +-
 Documentation/translations/zh_TW/process/4.Coding.rst |    2 +-
 5 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/Documentation/translations/zh_CN/process/4.Coding.rst b/Documentation/translations/zh_CN/process/4.Coding.rst
index 4cc35d410dbc..a00ad5d6b81e 100644
--- a/Documentation/translations/zh_CN/process/4.Coding.rst
+++ b/Documentation/translations/zh_CN/process/4.Coding.rst
@@ -216,7 +216,7 @@ Documentation/fault-injection/fault-injection.rst。
 可以在 https://sparse.wiki.kernel.org/index.php/Main_page 找到）,
 然后可以通过在make命令中添加“C=1”在代码上运行它。
 
-“Coccinelle”工具 :ref:`http://coccinelle.lip6.fr/ <devtools_coccinelle>`
+“Coccinelle”工具 :ref:`https://coccinelle.gitlabpages.inria.fr/website/ <devtools_coccinelle>`
 能够发现各种潜在的编码问题；它还可以为这些问题提出修复方案。在
 scripts/coccinelle目录下已经打包了相当多的内核“语义补丁”；运行
 “make coccicheck”将运行这些语义补丁并报告发现的任何问题。有关详细信息，请参阅
diff --git a/Documentation/translations/zh_TW/process/4.Coding.rst b/Documentation/translations/zh_TW/process/4.Coding.rst
index e90a6b51fb98..233e8718ed41 100644
--- a/Documentation/translations/zh_TW/process/4.Coding.rst
+++ b/Documentation/translations/zh_TW/process/4.Coding.rst
@@ -219,7 +219,7 @@ Documentation/fault-injection/fault-injection.rst。
 可以在 https://sparse.wiki.kernel.org/index.php/Main_page 找到）,
 然後可以通過在make命令中添加“C=1”在代碼上運行它。
 
-“Coccinelle”工具 :ref:`http://coccinelle.lip6.fr/ <devtools_coccinelle>`
+“Coccinelle”工具 :ref:`https://coccinelle.gitlabpages.inria.fr/website/ <devtools_coccinelle>`
 能夠發現各種潛在的編碼問題；它還可以爲這些問題提出修復方案。在
 scripts/coccinelle目錄下已經打包了相當多的內核“語義補丁”；運行
 “make coccicheck”將運行這些語義補丁並報告發現的任何問題。有關詳細信息，請參閱
diff --git a/Documentation/translations/it_IT/process/4.Coding.rst b/Documentation/translations/it_IT/process/4.Coding.rst
index 3126342c4b4a..a2ec35e016b7 100644
--- a/Documentation/translations/it_IT/process/4.Coding.rst
+++ b/Documentation/translations/it_IT/process/4.Coding.rst
@@ -329,7 +329,8 @@ Sparse deve essere installato separatamente (se il vostra distribuzione non
 lo prevede, potete trovarlo su https://sparse.wiki.kernel.org/index.php/Main_Page);
 può essere attivato sul codice aggiungendo "C=1" al comando make.
 
-Lo strumento "Coccinelle" (http://coccinelle.lip6.fr/) è in grado di trovare
+Lo strumento "Coccinelle" (https://coccinelle.gitlabpages.inria.fr/website/)
+è in grado di trovare
 una vasta varietà di potenziali problemi di codifica; e può inoltre proporre
 soluzioni per risolverli.  Un buon numero di "patch semantiche" per il kernel
 sono state preparate nella cartella scripts/coccinelle; utilizzando
diff --git a/Documentation/dev-tools/coccinelle.rst b/Documentation/dev-tools/coccinelle.rst
index c714780d458a..05614c469b47 100644
--- a/Documentation/dev-tools/coccinelle.rst
+++ b/Documentation/dev-tools/coccinelle.rst
@@ -34,7 +34,7 @@ of many distributions, e.g. :
 
 Some distribution packages are obsolete and it is recommended
 to use the latest version released from the Coccinelle homepage at
-http://coccinelle.lip6.fr/
+https://coccinelle.gitlabpages.inria.fr/website
 
 Or from Github at:
 
diff --git a/Documentation/translations/sp_SP/process/4.Coding.rst b/Documentation/translations/sp_SP/process/4.Coding.rst
index 7cc347c34354..6c3750ccdea2 100644
--- a/Documentation/translations/sp_SP/process/4.Coding.rst
+++ b/Documentation/translations/sp_SP/process/4.Coding.rst
@@ -336,7 +336,8 @@ https://sparse.wiki.kernel.org/index.php/Main_Page si su distribución no lo
 empaqueta); luego, puede ejecutarse en el código agregando "C=1" a su
 comando make.
 
-La herramienta "Coccinelle" (http://coccinelle.lip6.fr/) puede encontrar
+La herramienta "Coccinelle" (https://coccinelle.gitlabpages.inria.fr/website/)
+puede encontrar
 una amplia variedad de posibles problemas de codificación; también puede
 proponer correcciones para esos problemas. Bastantes "parches semánticos"
 para el kernel se han empaquetado en el directorio scripts/coccinelle;

Re: [cocci] [PATCH] coccinelle: update Coccinelle URL

[Julia Lawall]

On Tue, 10 Mar 2026, Julia Lawall wrote:

> The LIP6 URL no longer functions.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
>
> ---
>
> I used the UTF-8 encoding for the email.
> Let me know if this was not the right choice.

OK, this doesn't look good.  Sorry for the noise.  What is the proper
encoding?

thanks,
julia

>
>  Documentation/dev-tools/coccinelle.rst                |    2 +-
>  Documentation/translations/it_IT/process/4.Coding.rst |    3 ++-
>  Documentation/translations/sp_SP/process/4.Coding.rst |    3 ++-
>  Documentation/translations/zh_CN/process/4.Coding.rst |    2 +-
>  Documentation/translations/zh_TW/process/4.Coding.rst |    2 +-
>  5 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/process/4.Coding.rst b/Documentation/translations/zh_CN/process/4.Coding.rst
> index 4cc35d410dbc..a00ad5d6b81e 100644
> --- a/Documentation/translations/zh_CN/process/4.Coding.rst
> +++ b/Documentation/translations/zh_CN/process/4.Coding.rst
> @@ -216,7 +216,7 @@ Documentation/fault-injection/fault-injection.rst???
>  ????????? https://sparse.wiki.kernel.org/index.php/Main_page ?????????,
>  ?????????????????????make??????????????????C=1???????????????????????????
>
> -???Coccinelle????????? :ref:`http://coccinelle.lip6.fr/ <devtools_coccinelle>`
> +???Coccinelle????????? :ref:`https://coccinelle.gitlabpages.inria.fr/website/ <devtools_coccinelle>`
>  ?????????????????????????????????????????????????????????????????????????????????????????????
>  scripts/coccinelle?????????????????????????????????????????????????????????????????????
>  ???make coccicheck?????????????????????????????????????????????????????????????????????????????????????????????
> diff --git a/Documentation/translations/zh_TW/process/4.Coding.rst b/Documentation/translations/zh_TW/process/4.Coding.rst
> index e90a6b51fb98..233e8718ed41 100644
> --- a/Documentation/translations/zh_TW/process/4.Coding.rst
> +++ b/Documentation/translations/zh_TW/process/4.Coding.rst
> @@ -219,7 +219,7 @@ Documentation/fault-injection/fault-injection.rst???
>  ????????? https://sparse.wiki.kernel.org/index.php/Main_page ?????????,
>  ?????????????????????make??????????????????C=1???????????????????????????
>
> -???Coccinelle????????? :ref:`http://coccinelle.lip6.fr/ <devtools_coccinelle>`
> +???Coccinelle????????? :ref:`https://coccinelle.gitlabpages.inria.fr/website/ <devtools_coccinelle>`
>  ?????????????????????????????????????????????????????????????????????????????????????????????
>  scripts/coccinelle?????????????????????????????????????????????????????????????????????
>  ???make coccicheck?????????????????????????????????????????????????????????????????????????????????????????????
> diff --git a/Documentation/translations/it_IT/process/4.Coding.rst b/Documentation/translations/it_IT/process/4.Coding.rst
> index 3126342c4b4a..a2ec35e016b7 100644
> --- a/Documentation/translations/it_IT/process/4.Coding.rst
> +++ b/Documentation/translations/it_IT/process/4.Coding.rst
> @@ -329,7 +329,8 @@ Sparse deve essere installato separatamente (se il vostra distribuzione non
>  lo prevede, potete trovarlo su https://sparse.wiki.kernel.org/index.php/Main_Page);
>  pu?? essere attivato sul codice aggiungendo "C=1" al comando make.
>
> -Lo strumento "Coccinelle" (http://coccinelle.lip6.fr/) ?? in grado di trovare
> +Lo strumento "Coccinelle" (https://coccinelle.gitlabpages.inria.fr/website/)
> +?? in grado di trovare
>  una vasta variet?? di potenziali problemi di codifica; e pu?? inoltre proporre
>  soluzioni per risolverli.  Un buon numero di "patch semantiche" per il kernel
>  sono state preparate nella cartella scripts/coccinelle; utilizzando
> diff --git a/Documentation/dev-tools/coccinelle.rst b/Documentation/dev-tools/coccinelle.rst
> index c714780d458a..05614c469b47 100644
> --- a/Documentation/dev-tools/coccinelle.rst
> +++ b/Documentation/dev-tools/coccinelle.rst
> @@ -34,7 +34,7 @@ of many distributions, e.g. :
>
>  Some distribution packages are obsolete and it is recommended
>  to use the latest version released from the Coccinelle homepage at
> -http://coccinelle.lip6.fr/
> +https://coccinelle.gitlabpages.inria.fr/website
>
>  Or from Github at:
>
> diff --git a/Documentation/translations/sp_SP/process/4.Coding.rst b/Documentation/translations/sp_SP/process/4.Coding.rst
> index 7cc347c34354..6c3750ccdea2 100644
> --- a/Documentation/translations/sp_SP/process/4.Coding.rst
> +++ b/Documentation/translations/sp_SP/process/4.Coding.rst
> @@ -336,7 +336,8 @@ https://sparse.wiki.kernel.org/index.php/Main_Page si su distribuci??n no lo
>  empaqueta); luego, puede ejecutarse en el c??digo agregando "C=1" a su
>  comando make.
>
> -La herramienta "Coccinelle" (http://coccinelle.lip6.fr/) puede encontrar
> +La herramienta "Coccinelle" (https://coccinelle.gitlabpages.inria.fr/website/)
> +puede encontrar
>  una amplia variedad de posibles problemas de codificaci??n; tambi??n puede
>  proponer correcciones para esos problemas. Bastantes "parches sem??nticos"
>  para el kernel se han empaquetado en el directorio scripts/coccinelle;
>
>

Re: [cocci] [PATCH] coccinelle: update Coccinelle URL

[Akira Yokosawa]

[removed most CCs]

Hi Julia,

> On Tue, 10 Mar 2026, Julia Lawall wrote:
> 
>> The LIP6 URL no longer functions.
>>
>> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
>>
>> ---
>>
>> I used the UTF-8 encoding for the email.
>> Let me know if this was not the right choice.
> 
> OK, this doesn't look good.  Sorry for the noise.  What is the proper
> encoding?

Encoding itself looks good, but your patch has this in its header:

    MIME-Version: 1.0
    Content-Type: text/plain; charset=y
    Content-Transfer-Encoding: 8bit

, which should look like:

    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: 8bit

Didn't you say "y" to git-send-email's prompt of ...[UTF-8] ?

Thanks, Akira

> 
> thanks,
> julia

Re: [cocci] [PATCH] coccinelle: update Coccinelle URL

[Julia Lawall]

On Tue, 10 Mar 2026, Akira Yokosawa wrote:

> [removed most CCs]
>
> Hi Julia,
>
> > On Tue, 10 Mar 2026, Julia Lawall wrote:
> >
> >> The LIP6 URL no longer functions.
> >>
> >> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
> >>
> >> ---
> >>
> >> I used the UTF-8 encoding for the email.
> >> Let me know if this was not the right choice.
> >
> > OK, this doesn't look good.  Sorry for the noise.  What is the proper
> > encoding?
>
> Encoding itself looks good, but your patch has this in its header:
>
>     MIME-Version: 1.0
>     Content-Type: text/plain; charset=y
>     Content-Transfer-Encoding: 8bit
>
> , which should look like:
>
>     MIME-Version: 1.0
>     Content-Type: text/plain; charset=UTF-8
>     Content-Transfer-Encoding: 8bit
>
> Didn't you say "y" to git-send-email's prompt of ...[UTF-8] ?

Yes, I did.  I thought that would select the default...  Thanks for
letting me know.  Should I send it again, or is it ok as is?

thanks,
julia

>
> Thanks, Akira
>
> >
> > thanks,
> > julia
>

Re: [cocci] [PATCH] coccinelle: update Coccinelle URL

[Akira Yokosawa]

On Tue, 10 Mar 2026 12:46:46 +0100 (CET), Julia Lawall wrote:
> On Tue, 10 Mar 2026, Akira Yokosawa wrote:
> 
>> [removed most CCs]
>>
>> Hi Julia,
>>
>>> On Tue, 10 Mar 2026, Julia Lawall wrote:
>>>
>>>> The LIP6 URL no longer functions.
>>>>
>>>> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
>>>>
>>>> ---
>>>>
>>>> I used the UTF-8 encoding for the email.
>>>> Let me know if this was not the right choice.
>>>
>>> OK, this doesn't look good.  Sorry for the noise.  What is the proper
>>> encoding?
>>
>> Encoding itself looks good, but your patch has this in its header:
>>
>>     MIME-Version: 1.0
>>     Content-Type: text/plain; charset=y
>>     Content-Transfer-Encoding: 8bit
>>
>> , which should look like:
>>
>>     MIME-Version: 1.0
>>     Content-Type: text/plain; charset=UTF-8
>>     Content-Transfer-Encoding: 8bit
>>
>> Didn't you say "y" to git-send-email's prompt of ...[UTF-8] ?
> 
> Yes, I did.  I thought that would select the default...  Thanks for
> letting me know.  Should I send it again, or is it ok as is?

I'd just resend with a proper charset.

    Content-Type: text/plain; charset=y

would look confusing at best.

Thanks, Akira

> 
> thanks,
> julia
> 
>>
>> Thanks, Akira
>>
>>>
>>> thanks,
>>> julia
>>