From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: ophirmu@nvidia.com, robot@bytheb.org
Subject: [dpdk-test-report] |WARNING| pw75787 linux/mlx5: refactor VLAN
Date: Thu, 20 Aug 2020 12:29:35 -0400 [thread overview]
Message-ID: <20200820162935.11099-1-robot@bytheb.org> (raw)
In-Reply-To: <20200820145028.4090-13-ophirmu@nvidia.com>
From: robot@bytheb.org
Test-Label: travis-robot
Test-Status: WARNING
http://dpdk.org/patch/75787
_Travis build: failed_
Build URL: https://travis-ci.com/ovsrobot/dpdk/builds/180674850
prev parent reply other threads:[~2020-08-20 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200820145028.4090-13-ophirmu@nvidia.com>
2020-08-20 14:53 ` [dpdk-test-report] |SUCCESS| pw75787 [PATCH v1 13/13] " checkpatch
2020-08-20 16:29 ` 0-day Robot [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=20200820162935.11099-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=ophirmu@nvidia.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).