DPDK CI discussions
 help / color / Atom feed
From: "Wei, FangfangX" <fangfangx.wei@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, "Xu, Qian Q" <qian.q.xu@intel.com>,
	"Liu, Yong" <yong.liu@intel.com>
Subject: Re: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch
Date: Tue, 6 Dec 2016 06:34:45 +0000
Message-ID: <067B569323FEB248B5CB480E1954F4346BE93510@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1480944373-10233-8-git-send-email-thomas.monjalon@6wind.com>

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

Hi Thomas,



Here are some questiones about your scripts:

1. With the script "send-patch-report.sh", Can I send my perpatch build results to patchwork as checkpatch result in patchwork?

Such as, generate the GUI as blow:

[cid:image001.png@01D24FCC.01E4A4D0]

2. Must I create /etc/dpdk/ci.config before using your scripts?

   Because when I run it, it prompted following error message:

   /root/dpdk-cii/tools/load-ci-config.sh: line 5: /etc/dpdk/ci.config: No such file or directory

   /root/dpdk-cii/tools/load-ci-config.sh: line 6: /etc/dpdk/ci.config: No such file or directory



3. Some confuse about the parameters in "send-patch-report.sh":

           options:

                -t title    subject of the patch email

                -f from     sender of the patch email

                -m msgid    id of the patch email

                -p listid   mailing list publishing the patch

                -l label    title of the test

                -s status   one of these test results: SUCCESS, WARNING, FAILURE

                -d desc     few words to better describe the status



For example, about patch http://www.dpdk.org/dev/patchwork/patch/17673/

-t title    subject of the patch email

   Is it "[dpdk-dev,2/8] drivers/common/dpaa2: Sample descriptors for NXP DPAA2 SEC operations."?

-f from     sender of the patch email

   Is it the author who send the patch? In patch 17673, is it akhil.goyal@nxp.com<mailto:akhil.goyal@nxp.com>?

-m msgid    id of the patch email

   Is it the message-id of this patch? In patch 17673, is it 20161205125540.6419-3-akhil.goyal@nxp.com<mailto:20161205125540.6419-3-akhil.goyal@nxp.com>?

-p listid   mailing list publishing the patch

   Is it the receiver about this patch? In patch 17673, is it dev@dpdk.org<mailto:dev@dpdk.org>?



I try to send my result with script "send-patch-report.sh" with below command, but nothing happened.

echo "$report" | /root/dpdk-cii/tools/send-patch-report.sh -t "[dpdk-dev,2/8] drivers/common/dpaa2: Sample descriptors for NXP DPAA2 SEC operations." -f "akhil.goyal@nxp.com" -m "20161205125540.6419-3-akhil.goyal@nxp.com" -p "dev@dpdk.org" -l "Intel Per-patch compilation check" -s "SUCCESS" -d "Compilation OK"





Best Regards

Fangfang





-----Original Message-----
From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of Thomas Monjalon
Sent: Monday, December 5, 2016 9:26 PM
To: ci@dpdk.org
Subject: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch



This is the first test in this repository.

It runs on dpdk.org and use checkpatch.pl of Linux.



Note that the patch is not applied on a git tree for this basic test.



Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com<mailto:thomas.monjalon@6wind.com>>

---

tests/checkpatch.sh | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++++

1 file changed, 70 insertions(+)

create mode 100755 tests/checkpatch.sh



diff --git a/tests/checkpatch.sh b/tests/checkpatch.sh new file mode 100755 index 0000000..319da1e

--- /dev/null

+++ b/tests/checkpatch.sh

@@ -0,0 +1,70 @@

+#! /bin/sh -e

+

+# BSD LICENSE

+#

+# Copyright 2016 6WIND S.A.

+#

+# Redistribution and use in source and binary forms, with or without #

+modification, are permitted provided that the following conditions #

+are met:

+#

+#   * Redistributions of source code must retain the above copyright

+#     notice, this list of conditions and the following disclaimer.

+#   * Redistributions in binary form must reproduce the above copyright

+#     notice, this list of conditions and the following disclaimer in

+#     the documentation and/or other materials provided with the

+#     distribution.

+#   * Neither the name of 6WIND S.A. nor the names of its

+#     contributors may be used to endorse or promote products derived

+#     from this software without specific prior written permission.

+#

+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS #

+"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT #

+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR #

+A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT #

+OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, #

+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT #

+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, #

+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY #

+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT #

+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE #

+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

+

+print_usage () {

+    cat <<- END_OF_HELP

+    usage: $(basename $0) dpdk_dir < email

+

+    Check email-formatted patch from stdin.

+    This test runs checkpatch.pl of Linux via a script in dpdk_dir.

+    END_OF_HELP

+}

+

+while getopts h arg ; do

+    case $arg in

+          h ) print_usage ; exit 0 ;;

+          ? ) print_usage >&2 ; exit 1 ;;

+    esac

+done

+shift $(($OPTIND - 1))

+toolsdir=$(dirname $(readlink -m $0))/../tools

+dpdkdir=$1

+

+email=/tmp/$(basename $0 sh)$$

+$toolsdir/filter-patch-email.sh >$email trap "rm -f $email" INT EXIT

+

+eval $($toolsdir/parse-email.sh $email) # normal exit if no valid patch

+in the email [ -n "$subject" -a -n "$from" ] || exit 0

+

+failed=false

+report=$($dpdkdir/scripts/checkpatches.sh -q $email) || failed=true

+report=$(echo "$report" | sed '1,/^###/d')

+

+label='checkpatch'

+$failed && status='WARNING' || status='SUCCESS'

+$failed && desc='coding style issues' || desc='coding style OK'

+

+echo "$report" | $toolsdir/send-patch-report.sh \

+    -t "$subject" -f "$from" -m "$msgid" -p "$listid" \

+    -l "$label" -s "$status" -d "$desc"

--

2.7.0



[-- Attachment #1.2: Type: text/html, Size: 15482 bytes --]

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">Hi Thomas,<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">Here are some questiones about your scripts:<o:p></o:p></p>
<p class="MsoPlainText">1. With the script &quot;send-patch-report.sh&quot;, Can I send my perpatch build results to patchwork as checkpatch result in patchwork?<o:p></o:p></p>
<p class="MsoPlainText">Such as, generate the GUI as blow:<o:p></o:p></p>
<p class="MsoPlainText"><img width="384" height="153" id="Picture_x0020_2" src="cid:image001.png@01D24FCC.01E4A4D0"><o:p></o:p></p>
<p class="MsoPlainText">2. Must I create /etc/dpdk/ci.config before using your scripts?<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp; Because when I run it, it prompted following error message:<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp; /root/dpdk-cii/tools/load-ci-config.sh: line 5: /etc/dpdk/ci.config: No such file or directory<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp; /root/dpdk-cii/tools/load-ci-config.sh: line 6: /etc/dpdk/ci.config: No such file or directory<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">3. Some confuse about the parameters in &quot;send-patch-report.sh&quot;:<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;options:<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -t title&nbsp;&nbsp;&nbsp; subject of the patch email<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -f from&nbsp;&nbsp;&nbsp;&nbsp; sender of the patch email<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -m msgid&nbsp;&nbsp;&nbsp; id of the patch email<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -p listid&nbsp;&nbsp; mailing list publishing the patch<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;-l label&nbsp;&nbsp;&nbsp; title of the test<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -s status&nbsp;&nbsp; one of these test results: SUCCESS, WARNING, FAILURE<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -d desc&nbsp;&nbsp;&nbsp;&nbsp; few words to better describe the status<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">For example, about patch <a href="http://www.dpdk.org/dev/patchwork/patch/17673/">
http://www.dpdk.org/dev/patchwork/patch/17673/</a><o:p></o:p></p>
<p class="MsoPlainText">-t title&nbsp;&nbsp;&nbsp; subject of the patch email<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp; Is it &#8220;[dpdk-dev,2/8] drivers/common/dpaa2: Sample descriptors for NXP DPAA2 SEC operations.&#8221;?<o:p></o:p></p>
<p class="MsoPlainText">-f from&nbsp;&nbsp;&nbsp;&nbsp; sender of the patch email<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp; Is it the author who send the patch? In patch 17673, is it
<a href="mailto:akhil.goyal@nxp.com">akhil.goyal@nxp.com</a>?<o:p></o:p></p>
<p class="MsoPlainText">-m msgid&nbsp;&nbsp;&nbsp; id of the patch email<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp; Is it the message-id of this patch? In patch 17673, is it
<span style="font-size:10.5pt;font-family:&quot;Helvetica&quot;,sans-serif;color:#333333;background:white">
<a href="mailto:20161205125540.6419-3-akhil.goyal@nxp.com">20161205125540.6419-3-akhil.goyal@nxp.com</a>?<o:p></o:p></span></p>
<p class="MsoPlainText">-p listid&nbsp;&nbsp; mailing list publishing the patch<o:p></o:p></p>
<p class="MsoPlainText">&nbsp;&nbsp; Is it the receiver about this patch? In patch 17673, is it
<a href="mailto:dev@dpdk.org">dev@dpdk.org</a>?<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">I try to send my result with script &#8220;send-patch-report.sh&#8221; with below command, but nothing happened.<o:p></o:p></p>
<p class="MsoPlainText">echo &quot;$report&quot; | /root/dpdk-cii/tools/send-patch-report.sh -t &quot;[dpdk-dev,2/8] drivers/common/dpaa2: Sample descriptors for NXP DPAA2 SEC operations.&quot; -f &quot;akhil.goyal@nxp.com&quot; -m &quot;20161205125540.6419-3-akhil.goyal@nxp.com&quot; -p &quot;dev@dpdk.org&quot;
 -l &quot;Intel Per-patch compilation check&quot; -s &quot;SUCCESS&quot; -d &quot;Compilation OK&quot;<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">Best Regards<o:p></o:p></p>
<p class="MsoPlainText">Fangfang<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText"><a name="_MailEndCompose"><o:p>&nbsp;</o:p></a></p>
<p class="MsoPlainText"><a name="_____replyseparator"></a>-----Original Message-----<br>
From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of Thomas Monjalon<br>
Sent: Monday, December 5, 2016 9:26 PM<br>
To: ci@dpdk.org<br>
Subject: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch</p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">This is the first test in this repository.<o:p></o:p></p>
<p class="MsoPlainText">It runs on dpdk.org and use checkpatch.pl of Linux.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">Note that the patch is not applied on a git tree for this basic test.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">Signed-off-by: Thomas Monjalon &lt;<a href="mailto:thomas.monjalon@6wind.com"><span style="color:windowtext;text-decoration:none">thomas.monjalon@6wind.com</span></a>&gt;<o:p></o:p></p>
<p class="MsoPlainText">---<o:p></o:p></p>
<p class="MsoPlainText">tests/checkpatch.sh | 70 &#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;<o:p></o:p></p>
<p class="MsoPlainText">1 file changed, 70 insertions(&#43;)<o:p></o:p></p>
<p class="MsoPlainText">create mode 100755 tests/checkpatch.sh<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">diff --git a/tests/checkpatch.sh b/tests/checkpatch.sh new file mode 100755 index 0000000..319da1e<o:p></o:p></p>
<p class="MsoPlainText">--- /dev/null<o:p></o:p></p>
<p class="MsoPlainText">&#43;&#43;&#43; b/tests/checkpatch.sh<o:p></o:p></p>
<p class="MsoPlainText">@@ -0,0 &#43;1,70 @@<o:p></o:p></p>
<p class="MsoPlainText">&#43;#! /bin/sh -e<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;# BSD LICENSE<o:p></o:p></p>
<p class="MsoPlainText">&#43;#<o:p></o:p></p>
<p class="MsoPlainText">&#43;# Copyright 2016 6WIND S.A.<o:p></o:p></p>
<p class="MsoPlainText">&#43;#<o:p></o:p></p>
<p class="MsoPlainText">&#43;# Redistribution and use in source and binary forms, with or without #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;modification, are permitted provided that the following conditions #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;are met:<o:p></o:p></p>
<p class="MsoPlainText">&#43;#<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp; * Redistributions of source code must retain the above copyright<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp;&nbsp;&nbsp; notice, this list of conditions and the following disclaimer.<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp; * Redistributions in binary form must reproduce the above copyright<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp;&nbsp;&nbsp; notice, this list of conditions and the following disclaimer in<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp;&nbsp;&nbsp; the documentation and/or other materials provided with the<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp;&nbsp;&nbsp; distribution.<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp; * Neither the name of 6WIND S.A. nor the names of its<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp;&nbsp;&nbsp; contributors may be used to endorse or promote products derived<o:p></o:p></p>
<p class="MsoPlainText">&#43;#&nbsp;&nbsp;&nbsp;&nbsp; from this software without specific prior written permission.<o:p></o:p></p>
<p class="MsoPlainText">&#43;#<o:p></o:p></p>
<p class="MsoPlainText">&#43;# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;&quot;AS IS&quot; AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE #
<o:p></o:p></p>
<p class="MsoPlainText">&#43;OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;print_usage () {<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; cat &lt;&lt;- END_OF_HELP<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; usage: $(basename $0) dpdk_dir &lt; email<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; Check email-formatted patch from stdin.<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; This test runs checkpatch.pl of Linux via a script in dpdk_dir.<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; END_OF_HELP<o:p></o:p></p>
<p class="MsoPlainText">&#43;}<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;while getopts h arg ; do<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; case $arg in<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; h ) print_usage ; exit 0 ;;<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ? ) print_usage &gt;&amp;2 ; exit 1 ;;<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; esac<o:p></o:p></p>
<p class="MsoPlainText">&#43;done<o:p></o:p></p>
<p class="MsoPlainText">&#43;shift $(($OPTIND - 1))<o:p></o:p></p>
<p class="MsoPlainText">&#43;toolsdir=$(dirname $(readlink -m $0))/../tools<o:p></o:p></p>
<p class="MsoPlainText">&#43;dpdkdir=$1<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;email=/tmp/$(basename $0 sh)$$<o:p></o:p></p>
<p class="MsoPlainText">&#43;$toolsdir/filter-patch-email.sh &gt;$email trap &quot;rm -f $email&quot; INT EXIT<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;eval $($toolsdir/parse-email.sh $email) # normal exit if no valid patch
<o:p></o:p></p>
<p class="MsoPlainText">&#43;in the email [ -n &quot;$subject&quot; -a -n &quot;$from&quot; ] || exit 0<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;failed=false<o:p></o:p></p>
<p class="MsoPlainText">&#43;report=$($dpdkdir/scripts/checkpatches.sh -q $email) || failed=true
<o:p></o:p></p>
<p class="MsoPlainText">&#43;report=$(echo &quot;$report&quot; | sed '1,/^###/d')<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;label='checkpatch'<o:p></o:p></p>
<p class="MsoPlainText">&#43;$failed &amp;&amp; status='WARNING' || status='SUCCESS'<o:p></o:p></p>
<p class="MsoPlainText">&#43;$failed &amp;&amp; desc='coding style issues' || desc='coding style OK'<o:p></o:p></p>
<p class="MsoPlainText">&#43;<o:p></o:p></p>
<p class="MsoPlainText">&#43;echo &quot;$report&quot; | $toolsdir/send-patch-report.sh \<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; -t &quot;$subject&quot; -f &quot;$from&quot; -m &quot;$msgid&quot; -p &quot;$listid&quot; \<o:p></o:p></p>
<p class="MsoPlainText">&#43;&nbsp;&nbsp;&nbsp; -l &quot;$label&quot; -s &quot;$status&quot; -d &quot;$desc&quot;<o:p></o:p></p>
<p class="MsoPlainText">--<o:p></o:p></p>
<p class="MsoPlainText">2.7.0<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 7765 bytes --]

  reply index

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 17:02 [dpdk-ci] [PATCH 0/7] first scripts for CI integration Thomas Monjalon
2016-11-25 17:02 ` [dpdk-ci] [PATCH 1/7] tools: add mail filter Thomas Monjalon
2016-11-25 17:02 ` [dpdk-ci] [PATCH 2/7] tools: add mail parser Thomas Monjalon
2016-11-25 17:02 ` [dpdk-ci] [PATCH 3/7] config: add loader and template Thomas Monjalon
2016-11-25 17:02 ` [dpdk-ci] [PATCH 4/7] tools: add patchwork client Thomas Monjalon
2016-11-25 17:02 ` [dpdk-ci] [PATCH 5/7] tools: add per-patch report mailer Thomas Monjalon
2016-11-25 17:02 ` [dpdk-ci] [PATCH 6/7] tools: add patchwork integration Thomas Monjalon
2016-11-25 17:02 ` [dpdk-ci] [PATCH 7/7] tests: add checkpatch Thomas Monjalon
2016-12-01 13:44 ` [dpdk-ci] [PATCH v2 0/7] first scripts for CI integration Thomas Monjalon
2016-12-01 13:44   ` [dpdk-ci] [PATCH v2 1/7] tools: add mail filter Thomas Monjalon
2016-12-01 13:44   ` [dpdk-ci] [PATCH v2 2/7] tools: add mail parser Thomas Monjalon
2016-12-01 13:44   ` [dpdk-ci] [PATCH v2 3/7] config: add loader and template Thomas Monjalon
2016-12-01 13:44   ` [dpdk-ci] [PATCH v2 4/7] tools: add patchwork client Thomas Monjalon
2016-12-01 13:44   ` [dpdk-ci] [PATCH v2 5/7] tools: add per-patch report mailer Thomas Monjalon
2016-12-01 13:44   ` [dpdk-ci] [PATCH v2 6/7] tools: add patchwork integration Thomas Monjalon
2016-12-01 13:44   ` [dpdk-ci] [PATCH v2 7/7] tests: add checkpatch Thomas Monjalon
2016-12-01 16:58   ` [dpdk-ci] [PATCH v3 0/7] first scripts for CI integration Thomas Monjalon
2016-12-01 16:58     ` [dpdk-ci] [PATCH v3 1/7] tools: add mail filter Thomas Monjalon
2016-12-01 16:58     ` [dpdk-ci] [PATCH v3 2/7] tools: add mail parser Thomas Monjalon
2016-12-01 16:58     ` [dpdk-ci] [PATCH v3 3/7] config: add loader and template Thomas Monjalon
2016-12-01 16:58     ` [dpdk-ci] [PATCH v3 4/7] tools: add patchwork client Thomas Monjalon
2016-12-01 16:58     ` [dpdk-ci] [PATCH v3 5/7] tools: add per-patch report mailer Thomas Monjalon
2016-12-01 16:59     ` [dpdk-ci] [PATCH v3 6/7] tools: add patchwork integration Thomas Monjalon
2016-12-01 16:59     ` [dpdk-ci] [PATCH v3 7/7] tests: add checkpatch Thomas Monjalon
2016-12-05 13:26   ` [dpdk-ci] [PATCH v4 0/7] first scripts for CI integration Thomas Monjalon
2016-12-05 13:26     ` [dpdk-ci] [PATCH v4 1/7] tools: add mail filter Thomas Monjalon
2016-12-05 13:26     ` [dpdk-ci] [PATCH v4 2/7] tools: add mail parser Thomas Monjalon
2016-12-05 13:26     ` [dpdk-ci] [PATCH v4 3/7] config: add loader and template Thomas Monjalon
2016-12-05 13:26     ` [dpdk-ci] [PATCH v4 4/7] tools: add patchwork client Thomas Monjalon
2016-12-05 13:26     ` [dpdk-ci] [PATCH v4 5/7] tools: add per-patch report mailer Thomas Monjalon
2016-12-05 13:26     ` [dpdk-ci] [PATCH v4 6/7] tools: add patchwork integration Thomas Monjalon
2016-12-05 13:26     ` [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch Thomas Monjalon
2016-12-06  6:34       ` Wei, FangfangX [this message]
2016-12-06  8:40         ` Thomas Monjalon
2016-12-06  9:04           ` Wei, FangfangX
2016-12-07  5:48           ` Wei, FangfangX
2016-12-07  9:32             ` Thomas Monjalon
2016-12-08  9:02               ` Wei, FangfangX
2016-12-08 13:11                 ` Thomas Monjalon
2016-12-09  8:51                   ` Wei, FangfangX
2016-12-09  9:16                     ` Thomas Monjalon
2016-12-09 10:07                       ` Mcnamara, John
2016-12-09 10:11                         ` Thomas Monjalon
2016-12-09 12:11                           ` Mcnamara, John
2016-12-12  9:27                       ` Wei, FangfangX
2016-12-12  9:34                         ` Wei, FangfangX
2016-12-12  9:58                           ` Thomas Monjalon
2016-12-13  8:29                             ` Wei, FangfangX
2016-12-13  8:49                               ` Thomas Monjalon
2016-12-13  9:24                                 ` Wei, FangfangX
2016-12-21 11:45                                   ` Thomas Monjalon
2016-12-12  9:39                         ` Thomas Monjalon
2016-12-13  8:22                           ` Wei, FangfangX
2016-12-14 23:05     ` [dpdk-ci] [PATCH v5 0/9] first scripts for CI integration Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 1/9] tools: add mail filter Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 2/9] tools: add mail parser Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 3/9] config: add loader and template Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 4/9] tools: add patchwork client Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 5/9] tools: fix pwclient for proxy and python 3 Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 6/9] tools: add patch mail download Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 7/9] tools: add per-patch report mailer Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 8/9] tools: add patchwork integration Thomas Monjalon
2016-12-14 23:05       ` [dpdk-ci] [PATCH v5 9/9] tests: add checkpatch Thomas Monjalon
2016-12-21 11:46       ` [dpdk-ci] [PATCH v5 0/9] first scripts for CI integration Thomas Monjalon

Reply instructions:

You may reply publically 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=067B569323FEB248B5CB480E1954F4346BE93510@SHSMSX101.ccr.corp.intel.com \
    --to=fangfangx.wei@intel.com \
    --cc=ci@dpdk.org \
    --cc=qian.q.xu@intel.com \
    --cc=thomas.monjalon@6wind.com \
    --cc=yong.liu@intel.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

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox