From: "Wei, FangfangX" <fangfangx.wei@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "Xu, Qian Q" <qian.q.xu@intel.com>, "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] Fwd: Re: [dpdk-dev] [PATCH v3] app/test-crypto-perf: fix compilation under FreeBSD
Date: Mon, 13 Feb 2017 09:20:27 +0000 [thread overview]
Message-ID: <067B569323FEB248B5CB480E1954F4346EA0451B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1806668.usxBFJDS7m@xps13>
The new patches has been re-run today, I'll re-run the Deferred soon.
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Monday, February 13, 2017 5:00 PM
To: Wei, FangfangX <fangfangx.wei@intel.com>
Cc: Xu, Qian Q <qian.q.xu@intel.com>; ci@dpdk.org
Subject: Re: [dpdk-ci] Fwd: Re: [dpdk-dev] [PATCH v3] app/test-crypto-perf: fix compilation under FreeBSD
2017-02-13 02:18, Wei, FangfangX:
> From: Thomas Monjalon
> > There was (unfortunately) a compilation failure on FreeBSD.
> > I think that in such a case, the FreeBSD compilation must be skipped
> > in the automatic compilation tests. Or ideally it should not be
> > considered as a failure when testing a new patch, considering the
> > failure was already there.
> >
> > Now that it is fixed in the mainline, would it be possible to re-run
> > the tests for the recent pending patches? Note that the patchwork
> > result will be updated when sending a new report for the same patch
> > with the same test label.
>
> Hi Thomas,
> I find that the states of patches are RFC, Accepted, Changes
> Requested, Deferred, Superseded and New. I plan to re-run the patch，
> the state of which is New. Is that OK?
Please, could you re-run also the tests for the Deferred?
They will be New when 17.02 is released.
next prev parent reply other threads:[~2017-02-13 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 15:34 Thomas Monjalon
2017-02-13 2:18 ` Wei, FangfangX
2017-02-13 8:59 ` Thomas Monjalon
2017-02-13 9:20 ` Wei, FangfangX [this message]
2017-02-13 9:37 ` 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=067B569323FEB248B5CB480E1954F4346EA0451B@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 \
/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).