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>,
"Chen, WeichunX" <weichunx.chen@intel.com>
Subject: Re: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch
Date: Tue, 13 Dec 2016 08:22:33 +0000 [thread overview]
Message-ID: <067B569323FEB248B5CB480E1954F4346E9CD796@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1751971.7Nb5rNh5ze@xps13>
>> Actually, I'm not sure about it. In your environment, is there any configuration about sendmail in Linux?
>Nothing special.
>> >Yes it just an email to test-report@dpdk.org. Then this email is automatically parsed and integrated in patchwork by update-pw.sh running on the server.
>> >That's how the checkpatch test works (see tests/checkpatch.sh).
>>
>> If I send email with my own script, the receiver is test-report@dpdk.org, and the report format shows as below. Is this email also automatically parsed and integrated in patchwork on the server?
>>
>> Test-Label: Intel Per-patch compilation check
>> Test-Status: SUCCESS
>> http://dpdk.org/patch/17859
>>
>> _Compilation OK_
>>
>> The content about this compilation
>Yes it would work.
>What are you using to send this email?
>I'd like to understand why sendmail does not work for you.
I wrote a python script, which using smtplib module to send email:
smtp = smtplib.SMTP('Intel SMTP HOST')
next prev parent reply other threads:[~2016-12-13 8:22 UTC|newest]
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
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 [this message]
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 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=067B569323FEB248B5CB480E1954F4346E9CD796@SHSMSX103.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=weichunx.chen@intel.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
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).