From: <zhong.shiqi@zte.com.cn>
To: <Markus.Elfring@web.de>
Cc: wang.yi59@zte.com.cn, michal.lkml@markovi.net,
nicolas.palix@imag.fr, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, xue.zhihong@zte.com.cn,
cheng.shengyu@zte.com.cn, cocci@systeme.lip6.fr
Subject: Re: [Cocci] [PATCH v3] coccicheck: Support search for SmPL scripts withinselected directory hierarchy
Date: Sat, 26 Oct 2019 10:31:40 +0800 (CST) [thread overview]
Message-ID: <201910261031405235997@zte.com.cn> (raw)
In-Reply-To: <14f7a50d-63f5-343f-70e8-6b42ab5baa4c@web.de>
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
> > Allow defining COCCI as a directory to search SmPL scripts. Start a
> > corresponding file determination if the environment variable “COCCI”
> > contains an acceptable path.
>
> Can another wording fine-tuning matter for such a change description?
>
> * Allow defining the environment variable “COCCI” as a directory
> to search SmPL scripts.
>
> * Start a corresponding file determination if it contains an acceptable path.
Thanks,i think it would be better!
Best Regards,
zhong.shiqi
> Regards,
> Markus
[-- Attachment #2: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
prev parent reply other threads:[~2019-10-26 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 1:19 [Cocci] [PATCH v3] coccicheck: Support search for SmPL scripts within selected directory hierarchy zhongshiqi
2019-10-25 7:42 ` Markus Elfring
2019-10-25 9:38 ` [Cocci] [PATCH v3] coccicheck: Support search for SmPL scripts withinselected " zhong.shiqi
2019-10-25 11:06 ` [Cocci] [v3] coccicheck: Support search for SmPL scripts within selected " Markus Elfring
2019-10-26 2:31 ` zhong.shiqi [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=201910261031405235997@zte.com.cn \
--to=zhong.shiqi@zte.com.cn \
--cc=Markus.Elfring@web.de \
--cc=cheng.shengyu@zte.com.cn \
--cc=cocci@systeme.lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--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 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).