From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752586AbeACMSB (ORCPT + 1 other); Wed, 3 Jan 2018 07:18:01 -0500 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:6969 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751687AbeACMSA (ORCPT ); Wed, 3 Jan 2018 07:18:00 -0500 X-IronPort-AV: E=Sophos;i="5.45,501,1508796000"; d="scan'208";a="249966875" Date: Wed, 3 Jan 2018 13:17:54 +0100 (CET) From: Julia Lawall X-X-Sender: jll@hadrien To: SF Markus Elfring cc: cocci@systeme.lip6.fr, Gilles Muller , Himanshu Jha , Masahiro Yamada , Michal Marek , Nicolas Palix , Amitoj Kaur Chawla , LKML , kernel-janitors@vger.kernel.org Subject: Re: Coccinelle: Rename the script for a transformation of memory allocations In-Reply-To: Message-ID: References: <6423882b-20df-61fd-d7c6-ac1bb4ec891d@users.sourceforge.net> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="8323329-1024604736-1514981723=:23130" Content-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: --8323329-1024604736-1514981723=:23130 Content-Type: text/plain; CHARSET=UTF-8 Content-Transfer-Encoding: 8BIT Content-ID: 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 > --8323329-1024604736-1514981723=:23130-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julia Lawall Date: Wed, 03 Jan 2018 12:17:54 +0000 Subject: Re: Coccinelle: Rename the script for a transformation of memory allocations Message-Id: MIME-Version: 1 Content-Type: multipart/mixed; boundary="8323329-1024604736-1514981723=:23130" List-Id: References: <6423882b-20df-61fd-d7c6-ac1bb4ec891d@users.sourceforge.net> In-Reply-To: To: cocci@systeme.lip6.fr --8323329-1024604736-1514981723=:23130 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-ID: 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 > --8323329-1024604736-1514981723=:23130-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: julia.lawall@lip6.fr (Julia Lawall) Date: Wed, 3 Jan 2018 13:17:54 +0100 (CET) Subject: [Cocci] Coccinelle: Rename the script for a transformation of memory allocations In-Reply-To: References: <6423882b-20df-61fd-d7c6-ac1bb4ec891d@users.sourceforge.net> Message-ID: To: cocci@systeme.lip6.fr List-Id: cocci@systeme.lip6.fr 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 >