From: "Nicolas Palix (LIG)" <Nicolas.Palix@imag.fr>
To: Dafna Hirschfeld <dafna3@gmail.com>,
Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr,
michal.lkml@markovi.net, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Cc: outreachy-kernel@googlegroups.com
Subject: [Outreachy kernel] Re: [PATCH] Coccinelle: memdup: Fix typo in warning messages
Date: Thu, 1 Mar 2018 20:45:59 +0100 [thread overview]
Message-ID: <8cc75580-b29a-a599-4af1-6bb3783bc705@imag.fr> (raw)
In-Reply-To: <20180301085717.GA4508@gmail.com>
Le 01/03/2018 à 09:57, Dafna Hirschfeld a écrit :
> Replace 'kmemdep' with 'kmemdup' in warning messages.
>
> Signed-off-by: Dafna Hirschfeld <dafna3@gmail.com>
> Acked-by: Julia Lawall <julia.lawall@lip6.fr>
Acked-by: Nicolas Palix <nicolas.palix@imag.fr>
> ---
> scripts/coccinelle/api/memdup.cocci | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/coccinelle/api/memdup.cocci b/scripts/coccinelle/api/memdup.cocci
> index 1249b72..8fd6437 100644
> --- a/scripts/coccinelle/api/memdup.cocci
> +++ b/scripts/coccinelle/api/memdup.cocci
> @@ -56,10 +56,10 @@ statement S;
> p << r.p;
> @@
>
> -coccilib.org.print_todo(p[0], "WARNING opportunity for kmemdep")
> +coccilib.org.print_todo(p[0], "WARNING opportunity for kmemdup")
>
> @script:python depends on report@
> p << r.p;
> @@
>
> -coccilib.report.print_report(p[0], "WARNING opportunity for kmemdep")
> +coccilib.report.print_report(p[0], "WARNING opportunity for kmemdup")
>
--
Nicolas Palix
http://lig-membres.imag.fr/palix/
--
You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
To post to this group, send email to outreachy-kernel@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/8cc75580-b29a-a599-4af1-6bb3783bc705%40imag.fr.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2018-03-01 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 8:57 [Outreachy kernel] " Dafna Hirschfeld
2018-03-01 15:14 ` [Outreachy kernel] " Masahiro Yamada
2018-03-01 19:45 ` Nicolas Palix (LIG) [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=8cc75580-b29a-a599-4af1-6bb3783bc705@imag.fr \
--to=nicolas.palix@imag.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=dafna3@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@univ-grenoble-alpes.fr \
--cc=outreachy-kernel@googlegroups.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
all inboxes | Powered by JetHome®