From: Himanshu Jha <himanshujha199640@gmail.com>
To: yamada.masahiro@socionext.com
Cc: Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr,
nicolas.palix@imag.fr, michal.lkml@markovi.net,
cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org,
elfring@users.sourceforge.net,
Himanshu Jha <himanshujha199640@gmail.com>
Subject: [PATCH v2] Coccinelle: kzalloc-simple: Rename kzalloc-simple to zalloc-simple
Date: Sun, 14 Jan 2018 01:56:58 +0530 [thread overview]
Message-ID: <1515875218-9707-1-git-send-email-himanshujha199640@gmail.com> (raw)
Rename kzalloc-simple to zalloc-simple since now the rule is not
specific to kzalloc function only, but also to many other zero memory
allocating functions specified in the rule.
Suggested-by: SF Markus Elfring <elfring@users.sourceforge.net>
Signed-off-by: Himanshu Jha <himanshujha199640@gmail.com>
---
v2:
-generated the patch using -M flag for renaming.
-Since Markus earlier worked on renaming this patch adding his name too
.../coccinelle/api/alloc/{kzalloc-simple.cocci => zalloc-simple.cocci} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename scripts/coccinelle/api/alloc/{kzalloc-simple.cocci => zalloc-simple.cocci} (100%)
diff --git a/scripts/coccinelle/api/alloc/kzalloc-simple.cocci b/scripts/coccinelle/api/alloc/zalloc-simple.cocci
similarity index 100%
rename from scripts/coccinelle/api/alloc/kzalloc-simple.cocci
rename to scripts/coccinelle/api/alloc/zalloc-simple.cocci
--
2.7.4
next reply other threads:[~2018-01-13 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 20:26 Himanshu Jha [this message]
2018-01-14 9:00 ` [PATCH v2] Coccinelle: kzalloc-simple: Rename kzalloc-simple to zalloc-simple Julia Lawall
2018-01-16 14:35 ` Masahiro Yamada
2018-01-17 11:08 ` [v2] " SF Markus Elfring
2018-01-17 14:11 ` Himanshu Jha
2018-01-17 14:45 ` 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=1515875218-9707-1-git-send-email-himanshujha199640@gmail.com \
--to=himanshujha199640@gmail.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=elfring@users.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).