All of lore.kernel.org
 help / color / mirror / Atom feed
From: <zhong.shiqi@zte.com.cn>
To: <julia.lawall@lip6.fr>
Cc: wang.yi59@zte.com.cn, michal.lkml@markovi.net,
	nicolas.palix@imag.fr, linux-kernel@vger.kernel.org,
	xue.zhihong@zte.com.cn, cheng.shengyu@zte.com.cn,
	cocci@systeme.lip6.fr
Subject: Re: [Cocci] [PATCH v2] coccicheck:support $COCCI being defined as adirectory
Date: Thu, 24 Oct 2019 16:02:06 +0800 (CST)	[thread overview]
Message-ID: <201910241602064396894@zte.com.cn> (raw)
In-Reply-To: <alpine.DEB.2.21.1910240816040.2771@hadrien>


[-- Attachment #1.1: Type: text/plain, Size: 1740 bytes --]

> On Thu, 24 Oct 2019, zhongshiqi wrote:
>
> > Put a modification in scripts/coccicheck which supports users in
> > configuring COCCI parameter as a directory to traverse files in
> > directory whose next level directory contains rule files with Suffix of
> > cocci.
>
> While I thought the original was fine, if we are going to strive for
> perfection, there are some things that could be changed.  First there
> should be a space in the subject line after the :
>
> Second the commit log could be more concise as:
>
> Allow defining COCCI as a directory that contains .cocci files.
>
> In general, at least in simple cases, it is not necessary to mention the
> name of the file you are modifying in the comit log, because one can see
> that just below from looking at the diffstat and the patch.
>
> thanks,
> julia
>

Thank you,it is very good for me

Best Regards,
zhong.shiqi

> >
> > Signed-off-by: zhongshiqi <zhong.shiqi@zte.com.cn>
> > ---
> > Changes in v2:
> >         1.fix patch subject according to the reply by Markus
> >         <Markus.Elfring@web.de>
> >         2.change description in “imperative mood”
> >
> >  scripts/coccicheck | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/scripts/coccicheck b/scripts/coccicheck
> > index e04d328..a1c4197 100755
> > --- a/scripts/coccicheck
> > +++ b/scripts/coccicheck
> > @@ -257,6 +257,10 @@ if [ "$COCCI" = "" ] ; then
> >      for f in `find $srctree/scripts/coccinelle/ -name '*.cocci' -type f | sort`; do
> >      coccinelle $f
> >      done
> > +elif [ -d "$COCCI" ] ; then
> > +    for f in `find $COCCI/ -name '*.cocci' -type f | sort`; do
> > +    coccinelle $f
> > +    done
> >  else
> >      coccinelle $COCCI
> >  fi
> > --
> > 2.9.5
> >
> >

[-- Attachment #2: Type: text/plain, Size: 136 bytes --]

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

  parent reply	other threads:[~2019-10-24  8:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  6:04 [Cocci] [PATCH v2] coccicheck:support $COCCI being defined as a directory zhongshiqi
2019-10-24  6:04 ` zhongshiqi
2019-10-24  6:19 ` [Cocci] " Julia Lawall
2019-10-24  6:19   ` Julia Lawall
2019-10-24  7:55   ` [Cocci] [PATCH v2] coccicheck: support " Markus Elfring
2019-10-24  7:55     ` Markus Elfring
2019-10-24  7:55     ` Markus Elfring
2019-10-24  7:58     ` [Cocci] " Julia Lawall
2019-10-24  7:58       ` Julia Lawall
2019-10-24  7:58       ` Julia Lawall
2019-10-24  9:11       ` [Cocci] [v2] " Markus Elfring
2019-10-24  9:11         ` Markus Elfring
2019-10-24  9:11         ` Markus Elfring
2019-10-24  8:02   ` zhong.shiqi [this message]
2019-10-24  7:06 ` [Cocci] [PATCH v2] " Markus Elfring
2019-10-24  7:06   ` Markus Elfring
2019-10-24  7:06   ` Markus Elfring
2019-10-24  8:03   ` [Cocci] [PATCH v2] coccicheck: support $COCCI being defined as adirectory zhong.shiqi
2019-10-24  9:23     ` [Cocci] [v2] " Markus Elfring
2019-10-24  9:23       ` Markus Elfring
2019-10-24  9:23       ` Markus Elfring
2019-10-24  9:58       ` [Cocci] " zhong.shiqi
2019-10-24 10:52         ` [Cocci] [v2] coccicheck: support $COCCI being defined as a directory Markus Elfring
2019-10-24 10:52           ` Markus Elfring
2019-10-24 10:52           ` 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=201910241602064396894@zte.com.cn \
    --to=zhong.shiqi@zte.com.cn \
    --cc=cheng.shengyu@zte.com.cn \
    --cc=cocci@systeme.lip6.fr \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=nicolas.palix@imag.fr \
    --cc=wang.yi59@zte.com.cn \
    --cc=xue.zhihong@zte.com.cn \
    /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.