From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: roy.fan.zhang@intel.com, robot@bytheb.org
Subject: [dpdk-test-report] || pw76573 fips_validation: update GCM test
Date: Fri, 4 Sep 2020 14:27:37 -0400 [thread overview]
Message-ID: <20200904182737.11613-1-robot@bytheb.org> (raw)
In-Reply-To: <20200904160945.24590-3-roy.fan.zhang@intel.com>
From: robot@bytheb.org
Test-Label: travis-robot
Test-Status:
http://dpdk.org/patch/76573
_Travis build: errored_
Build URL: https://travis-ci.com/ovsrobot/dpdk/builds/182811089
next parent reply other threads:[~2020-09-04 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200904160945.24590-3-roy.fan.zhang@intel.com>
2020-09-04 18:27 ` 0-day Robot [this message]
2020-09-08 23:43 ` [dpdk-test-report] |SUCCESS| pw76573 [dpdk-dev v2 2/2] " checkpatch
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=20200904182737.11613-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=roy.fan.zhang@intel.com \
--cc=test-report@dpdk.org \
/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).