All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: cocci@systeme.lip6.fr, Gilles Muller <Gilles.Muller@lip6.fr>,
	Himanshu Jha <himanshujha199640@gmail.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Michal Marek <michal.lkml@markovi.net>,
	Nicolas Palix <nicolas.palix@imag.fr>,
	Amitoj Kaur Chawla <amitoj1606@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: Coccinelle: Rename the script for a transformation of memory allocations
Date: Wed, 3 Jan 2018 13:17:54 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1801031315230.23130@hadrien> (raw)
In-Reply-To: <d576069f-2786-d1fe-e015-9d7ed63e5d94@users.sourceforge.net>

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



On Wed, 3 Jan 2018, SF Markus Elfring wrote:

> >> rename from scripts/coccinelle/api/alloc/kzalloc-simple.cocci
> >> rename to scripts/coccinelle/api/alloc/use zalloc functions with extra changes.cocci
> >
> > NACK.
>
> It seems that we need a few more tries to achieve the desired consensus.
>
>
> > The name is too long
>
> How would you like to express the provided functionality in a
> “permanent” file name?

I have not idea what a permanent file name is.  The current name could be
better without the leading k, but otherwise I think it is fine.

>
>
> > and should not contain spaces.
>
> May names contain space characters generally for Linux files?

I have never seen a file name with spaces in the Linux kernel, but I don't
know an easy way to check for that.  But personally, I really dislike
them, and I will nack any patch that proposes to use one.

julia

>
> Regards,
> Markus
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

WARNING: multiple messages have this Message-ID (diff)
From: Julia Lawall <julia.lawall@lip6.fr>
To: cocci@systeme.lip6.fr
Subject: Re: Coccinelle: Rename the script for a transformation of memory allocations
Date: Wed, 03 Jan 2018 12:17:54 +0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1801031315230.23130@hadrien> (raw)
In-Reply-To: <d576069f-2786-d1fe-e015-9d7ed63e5d94@users.sourceforge.net>

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



On Wed, 3 Jan 2018, SF Markus Elfring wrote:

> >> rename from scripts/coccinelle/api/alloc/kzalloc-simple.cocci
> >> rename to scripts/coccinelle/api/alloc/use zalloc functions with extra changes.cocci
> >
> > NACK.
>
> It seems that we need a few more tries to achieve the desired consensus.
>
>
> > The name is too long
>
> How would you like to express the provided functionality in a
> “permanent” file name?

I have not idea what a permanent file name is.  The current name could be
better without the leading k, but otherwise I think it is fine.

>
>
> > and should not contain spaces.
>
> May names contain space characters generally for Linux files?

I have never seen a file name with spaces in the Linux kernel, but I don't
know an easy way to check for that.  But personally, I really dislike
them, and I will nack any patch that proposes to use one.

julia

>
> Regards,
> Markus
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

WARNING: multiple messages have this Message-ID (diff)
From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Coccinelle: Rename the script for a transformation of memory allocations
Date: Wed, 3 Jan 2018 13:17:54 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1801031315230.23130@hadrien> (raw)
In-Reply-To: <d576069f-2786-d1fe-e015-9d7ed63e5d94@users.sourceforge.net>



On Wed, 3 Jan 2018, SF Markus Elfring wrote:

> >> rename from scripts/coccinelle/api/alloc/kzalloc-simple.cocci
> >> rename to scripts/coccinelle/api/alloc/use zalloc functions with extra changes.cocci
> >
> > NACK.
>
> It seems that we need a few more tries to achieve the desired consensus.
>
>
> > The name is too long
>
> How would you like to express the provided functionality in a
> ?permanent? file name?

I have not idea what a permanent file name is.  The current name could be
better without the leading k, but otherwise I think it is fine.

>
>
> > and should not contain spaces.
>
> May names contain space characters generally for Linux files?

I have never seen a file name with spaces in the Linux kernel, but I don't
know an easy way to check for that.  But personally, I really dislike
them, and I will nack any patch that proposes to use one.

julia

>
> Regards,
> Markus
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2018-01-03 12:18 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26 21:40 [PATCH v2] Coccinelle: kzalloc-simple: Add all zero allocating functions Himanshu Jha
2017-12-26 21:40 ` [Cocci] " Himanshu Jha
2017-12-26 21:52 ` Julia Lawall
2017-12-26 21:52   ` [Cocci] " Julia Lawall
2017-12-29 17:22 ` Masahiro Yamada
2017-12-29 17:22   ` [Cocci] " Masahiro Yamada
2017-12-29 17:49   ` Julia Lawall
2017-12-29 17:49     ` [Cocci] " Julia Lawall
2018-01-02 14:25   ` Rename the SmPL script “kzalloc-….cocci”? SF Markus Elfring
2018-01-02 14:25     ` SF Markus Elfring
2018-01-02 14:28     ` Julia Lawall
2018-01-02 14:28       ` [Cocci] " Julia Lawall
2018-01-02 14:28       ` Julia Lawall
2018-01-02 14:38       ` SF Markus Elfring
2018-01-02 14:38         ` SF Markus Elfring
2018-01-02 14:43         ` Julia Lawall
2018-01-02 14:43           ` [Cocci] " Julia Lawall
2018-01-02 14:43           ` Julia Lawall
2018-01-02 15:00           ` SF Markus Elfring
2018-01-02 15:00             ` SF Markus Elfring
2018-01-08  9:55           ` SF Markus Elfring
2018-01-08  9:55             ` SF Markus Elfring
2018-01-03 11:55       ` [PATCH] Coccinelle: Rename the script for a transformation of memory allocations SF Markus Elfring
2018-01-03 11:55         ` SF Markus Elfring
2018-01-03 12:02         ` Julia Lawall
2018-01-03 12:02           ` [Cocci] " Julia Lawall
2018-01-03 12:02           ` Julia Lawall
2018-01-03 12:13           ` SF Markus Elfring
2018-01-03 12:13             ` SF Markus Elfring
2018-01-03 12:17             ` Julia Lawall [this message]
2018-01-03 12:17               ` [Cocci] " Julia Lawall
2018-01-03 12:17               ` Julia Lawall
2018-01-03 12:31               ` SF Markus Elfring
2018-01-03 12:31                 ` SF Markus Elfring
2018-01-03 12:40                 ` Julia Lawall
2018-01-03 12:40                   ` [Cocci] " Julia Lawall
2018-01-03 12:40                   ` Julia Lawall
2018-01-03 12:45                   ` SF Markus Elfring
2018-01-03 12:45                     ` SF Markus Elfring
2018-01-04  8:36                   ` SF Markus Elfring
2018-01-04  8:36                     ` SF Markus Elfring
2018-01-04  8:54                     ` Julia Lawall
2018-01-04  8:54                       ` [Cocci] " Julia Lawall
2018-01-04  8:54                       ` Julia Lawall
2018-01-04  9:43                       ` SF Markus Elfring
2018-01-04  9:43                         ` SF Markus Elfring
2018-01-17 16:47   ` [v2] Coccinelle: zalloc-simple: Safer transformations with SmPL SF Markus Elfring
2018-01-17 16:47     ` SF Markus Elfring
2018-01-19 16:14   ` Coccinelle: zalloc-simple: Checking consequences from the usage of at signs in Python strings SF Markus Elfring
2018-01-19 16:14     ` SF Markus Elfring
2018-01-19 16:18     ` Julia Lawall
2018-01-19 16:18       ` [Cocci] " Julia Lawall
2018-01-19 16:18       ` Julia Lawall
2018-01-19 16:43       ` SF Markus Elfring
2018-01-19 16:43         ` SF Markus Elfring
2018-01-24  8:41       ` SF Markus Elfring
2018-01-24  8:41         ` SF Markus Elfring
2018-01-31 17:28   ` [v2] Coccinelle: zalloc-simple: Delete function “kmem_cache_alloc” from SmPL rules SF Markus Elfring
2018-01-31 17:28     ` [Cocci] " SF Markus Elfring
2018-01-31 17:28     ` [v2] Coccinelle: zalloc-simple: Delete function =?UTF-8?B?4oCca21lbV9jYWNoZV9hbGxvY SF Markus Elfring
2018-01-31 17:38     ` [v2] Coccinelle: zalloc-simple: Delete function “kmem_cache_alloc” from SmPL rules Julia Lawall
2018-01-31 17:38       ` [Cocci] " Julia Lawall
2018-01-31 17:38       ` =?UTF-8?Q?Re=3A_=5Bv2=5D_Coccinelle=3A_zalloc-simple=3A_Delete_function_=E2=80=9Ckmem=5Fcache=5Fallo Julia Lawall
2018-01-31 17:53       ` [v2] Coccinelle: zalloc-simple: Delete function “kmem_cache_alloc” from SmPL rules SF Markus Elfring
2018-01-31 17:53         ` [v2] Coccinelle: zalloc-simple: Delete function =?UTF-8?B?4oCca21lbV9jYWNoZV9hbGxvY SF Markus Elfring
2018-02-01  9:35   ` [PATCH] Coccinelle: zalloc-simple: Delete function "kmem_cache_alloc" from SmPL rules SF Markus Elfring
2018-02-01  9:35     ` SF Markus Elfring
2018-02-01  9:40     ` Julia Lawall
2018-02-01  9:40       ` [Cocci] " Julia Lawall
2018-02-01  9:40       ` Julia Lawall
2018-02-01 10:17       ` SF Markus Elfring
2018-02-01 10:17         ` SF Markus Elfring
2018-02-01 10:27         ` Julia Lawall
2018-02-01 10:27           ` [Cocci] " Julia Lawall
2018-02-01 10:27           ` Julia Lawall
2018-02-01 11:00           ` SF Markus Elfring
2018-02-01 11:00             ` SF Markus Elfring
2018-02-03  7:22           ` Coccinelle: zalloc-simple: Checking consistency for " SF Markus Elfring
2018-02-03  7:22             ` SF Markus Elfring

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=alpine.DEB.2.20.1801031315230.23130@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=Gilles.Muller@lip6.fr \
    --cc=amitoj1606@gmail.com \
    --cc=cocci@systeme.lip6.fr \
    --cc=elfring@users.sourceforge.net \
    --cc=himanshujha199640@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=nicolas.palix@imag.fr \
    --cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.