From: "Liu, Yong" <yong.liu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, "Wei, FangfangX" <fangfangx.wei@intel.com>
Subject: Re: [dpdk-ci] check patch status duplicated in mailing list
Date: Wed, 16 Nov 2016 01:35:03 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E603283EE@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <2888549.A4ztrYCj9Y@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, November 15, 2016 5:24 PM
> To: Liu, Yong
> Cc: ci@dpdk.org
> Subject: Re: check patch status duplicated in mailing list
>
> 2016-11-15 03:32, Liu, Yong:
> > Hi Thomas,
> > There're two checkpatch report in this mailing now. One of them is
> included in patchset status report.
> > These two reports are focusing on the same thing and sometimes
> mismatched in the result.
> > I guess it is caused by different version of checkpatch scripts have
> different rules, ours version is 0.32.
> >
> > Since newer checkpatch report has been integrated with patch work system.
> I suggest to remove checkpatch in patchset report. Looking for your option.
>
> Yes I was going to suggest to remove checkpatch from Intel checks.
>
> Also could we improve the check description?
> Test-Label: Intel Niantic on Fedora
> If it is doing only some compilation checks, it should be
> Test-Label: Intel compilation on Fedora
>
Sure, we will change the description for patch set build check.
BTW, we have enhanced our patch set build check from only build once to build with each patch.
This new report will take the place of the existing one in the near future.
We will look for you suggestions on it:)
> Later this week, I would like to share the scripts used for checkpatch
> so that we can have the Intel checks integrated in patchwork.
>
> PS: moving this discussion on ci@dpdk.org
> We should post only the test reports on test-report@dpdk.org
> and discuss on ci@dpdk.org.
prev parent reply other threads:[~2016-11-16 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86228AFD5BCD8E4EBFD2B90117B5E81E60326B6D@SHSMSX103.ccr.corp.intel.com>
2016-11-15 9:23 ` Thomas Monjalon
2016-11-16 1:35 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E603283EE@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=ci@dpdk.org \
--cc=fangfangx.wei@intel.com \
--cc=thomas.monjalon@6wind.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).