cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Jessica Yu <jeyu@kernel.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: michal.lkml@markovi.net, nicolas.palix@imag.fr,
	maennich@google.com, linux-kernel@vger.kernel.org,
	Markus.Elfring@web.de, gregkh@linuxfoundation.org,
	cocci@systeme.lip6.fr
Subject: Re: [Cocci] [PATCH] scripts: add_namespace: Fix coccicheck failed
Date: Mon, 7 Oct 2019 15:15:42 +0200	[thread overview]
Message-ID: <20191007131542.GA30078@linux-8ccs> (raw)
In-Reply-To: <20191006044456.57608-1-yuehaibing@huawei.com>

+++ YueHaibing [06/10/19 12:44 +0800]:
>Now all scripts in scripts/coccinelle to be automatically called
>by coccicheck. However new adding add_namespace.cocci does not
>support report mode, which make coccicheck failed.
>This add "virtual report" to  make the coccicheck go ahead smoothly.
>
>Fixes: eb8305aecb95 ("scripts: Coccinelle script for namespace dependencies.")
>Acked-by: Julia Lawall <julia.lawall@lip6.fr>
>Signed-off-by: YueHaibing <yuehaibing@huawei.com>

Thanks for the fix!

If there are no complaints, I'll queue this up in the modules tree for -rc3.

Jessica
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  parent reply	other threads:[~2019-10-07 20:42 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28  9:42 [Cocci] [RFC PATCH] scripts: Fix coccicheck failed YueHaibing
2019-09-28 12:43 ` Julia Lawall
2019-09-29  2:04   ` Yuehaibing
2019-09-29 16:32     ` Julia Lawall
2019-09-29 18:00       ` Markus Elfring
2019-09-29 18:05         ` Julia Lawall
2019-09-29 18:18           ` [Cocci] [RFC] " Markus Elfring
2019-09-30  2:32       ` [Cocci] [RFC PATCH] " Yuehaibing
2019-10-01 12:57         ` Matthias Maennich
2019-10-01 15:33           ` [Cocci] [RFC] " Markus Elfring
2019-10-01 13:01         ` [Cocci] [RFC PATCH] " Julia Lawall
2019-10-03 11:57           ` Masahiro Yamada
2019-10-03 12:22             ` Julia Lawall
2019-10-04  2:32               ` Masahiro Yamada
2019-10-05 11:17                 ` [Cocci] [RFC] " Markus Elfring
2019-10-05 12:26                   ` Julia Lawall
2019-10-05 17:49                     ` Markus Elfring
2019-10-05 17:49                     ` Markus Elfring
2019-10-06  5:21                     ` Markus Elfring
2019-10-06  5:28                       ` Julia Lawall
2019-10-06  5:34                         ` Markus Elfring
2019-10-06  7:30                           ` Greg Kroah-Hartman
2019-10-06  4:23                 ` [Cocci] [RFC PATCH] " Yuehaibing
2019-10-06  4:44                 ` [Cocci] [PATCH] scripts: add_namespace: " YueHaibing
2019-10-06  6:40                   ` Markus Elfring
2019-10-06  6:44                     ` Julia Lawall
2019-10-06  7:00                       ` [Cocci] " Markus Elfring
2019-10-06 11:09                   ` [Cocci] [PATCH] " Matthias Maennich
2019-10-07 13:15                   ` Jessica Yu [this message]
2019-10-03 16:30             ` [Cocci] [RFC] scripts: " Markus Elfring
2019-10-03 16:30             ` Markus Elfring
2019-10-03 19:35               ` Julia Lawall
2019-10-04  8:23                 ` Markus Elfring
2019-09-29  8:20 ` [Cocci] [RFC PATCH] " Markus Elfring
2019-09-29 13:12 ` Markus Elfring
2019-09-29 16:40   ` Julia Lawall
2019-10-02  7:09     ` [Cocci] [PATCH 0/2] Coccinelle: Extend directory hierarchy Markus Elfring
2019-10-02  7:10       ` [Cocci] [PATCH 1/2] Coccinelle: Move the SmPL script “add_namespace.cocci” into a new directory Markus Elfring
2019-10-02  7:12       ` [Cocci] [PATCH 2/2] Coccinelle: Move coccicheck directories into a new subdirectory 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=20191007131542.GA30078@linux-8ccs \
    --to=jeyu@kernel.org \
    --cc=Markus.Elfring@web.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maennich@google.com \
    --cc=michal.lkml@markovi.net \
    --cc=nicolas.palix@imag.fr \
    --cc=yuehaibing@huawei.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).